2010/1/26 pancake <pancake_AT_youterm.com>:
>
>
> On Jan 26, 2010, at 8:10 AM, Daniel Bainton <dpb_AT_driftaway.org> wrote:
>
>> 2010/1/25 pancake <pancake_AT_youterm.com>:
>>>
>>> I have been using make(1) and acr(1) for most of my projects for a long
>>> while
>>
>> acr seems to have the OS guessing quite bad. It checks if uname is the
>> GNU version and then adds -gnu to the system type if it is? What if
>> the system is a uClibc based one that uses the GNU version of uname?
>>
>> gcc -dumpmachine would be a better way IMO (though probably not the
>> best anyway, atleast if the system has some other compiler than gcc..)
>>
> It cannot depend on gcc. What about crosscompiling? What about non-C
> projects?
>
> That string is just orientative imho. So i simplified the algorithm to
> handle most common situations.
>
> The code in autoconf that do this is really painful. And i dont really get
> the point of having a moré accurate and complex host string resolution.
>
> Do you have any other proposal to enhace it? With --target, --host and
> --build you can change the default string.
I can't think of a better way currently, but for example stali, that
will give the wrong build string.
-- DanielReceived on Tue Jan 26 2010 - 08:11:41 UTC
This archive was generated by hypermail 2.2.0 : Tue Jan 26 2010 - 08:24:01 UTC