Re: DO NOT use file format of /bin/sh for x32 detection!

[Earnie]

On 2/28/2018 7:53 PM, James Clarke wrote:
> On 1 Mar 2018, at 00:50, Ben Elliston <address@hidden> wrote:
>>
>> On Wed, Feb 28, 2018 at 03:55:57PM +0100, Thorsten Glaser wrote:
>>
>>> I really have no other idea that???s in scope. After all,
>>> CC_FOR_BUILD is the *only* tool guaranteed to correspond to the
>>> target (in FreeWRT speak; --build= in GNU autotools speak) system.
>>
>> We're trying to guess the build system, not the target. When
>> configuring cross-tools, it has always been necessary to specify the
>> target triplet with --target.
> 
> Thorsten is not doing a cross-compile; the native system is x32, with an
> x32->x32 compiler. The exception is that the odd binary is amd64 rather than
> x32, so it's not a *pure* system, but build=host=target=x32.
> 

Am I understanding correctly; your compiler is a 32bit compiler on a
64bit OS whose uname returns the 64bit OS system?  I don't think
config.guess should manage this and it is up to the end user to specify
the --build.  The fact that a 32bit compiler is running on a 64bit
system is a bit of a stretch for any method of guessing what the build
system is.  We don't want to set a precedent of using any executable of
a compiler to determine the build.

-- 
Earnie