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

[James Clarke]

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.

James

> In a native environment, there should be numerous ways of determining
> the system ABI (if it matters) without invoking a C compiler (which is
> often not installed, leading to spurious problem reports from users).
> 
> Ben