Re: [Mingw-cross-env-list] Specifying --build (was: make curl fails)

[Tony Theodore]

On 27 November 2011 09:28, Volker Grabsch <address@hidden> wrote:
> Tony Theodore schrieb:
>> On 27 November 2011 07:26, Mark Brand <address@hidden> wrote:
>> >> Shall we just install the config.guess from gcc to
>> >> <mcedir>/usr/bin/config.guess and add the following to the main
>> >> Makefile?:
>> >>
>> >>    BUILD      := $(shell $(PWD)/usr/bin/config.guess)
>> >
>> > This better I think:
>> >
>> >    BUILD      := $(shell $(PREFIX)/bin/config.guess)
>
> This is better, but I still think that
>
>     --build=`$(TARGET)-config.guess`
>
> is more clear than our new variable
>
>     --build=$(BUILD)
>
> In other words, I think that our BUILD variable would
> introduce an indirection which makes things less
> transparent without providing any real benefit.

Also, a variable in the main Makefile won't be initialised since the
script won't exist when it's first called.

[...]
>> There's another script, config.sub. I'm not sure what it does, but it
>> seems to be a complement to config.guess. I imagine that if we install
>> them in the same place, all will be fine.
>
> Would you mind investigating further in how far those
> two scripts are connected. Also, do we really need a
> system-wide config.sub, or are the local versions of the
> respective packages sufficient if we already provide the
> --build option to ./configure?

It seems config.sub is used by configure to validate the output of
config.guess and I imagine that it would fail where these are
outdated. The main reason having both would be useful is that we could
get rid of all the src/*-config-update.patch files and simply copy
these over where necessary.

Comments in the file also suggest that a system wide version is ideal:

# This file is (in principle) common to ALL GNU software.
...
# This file is supposed to be the same for all GNU packages

Cheers,

Tony