[again as plain text]
Ah, I didn't realize any C or C++ code could be configured for other than a
specific processor but I guess that makes sense -- it is Makefile, config.h,
and such that are being modified, not the .o files, and they might be the same
across many configurations, like if the compiler command lines and #defines can
be the same, like if there is no need to know the size of a pointer or the
endianness, etc.. I guess more code should work this way if possible. Thanks
Andrew.
(Obviously a lot of source code is independent of pointer size, endianness, but
I haven't seen such configure processor=none use.).
- Jay
> Date: Tue, 17 Jun 2008 13:39:42 -0400
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: configuring in-tree gmp/mpfr with "none"?
> CC: gcc@gcc.gnu.org
>
> On Sun, Jun 15, 2008 at 12:49 PM, Jay wrote:
>>
>> When gcc configures the in-tree gmp/mpfr, why
>> does it use --host=none-${host_vendor}-${host_os}
>> --target=none-${host_vendor}-${host_os}
>>
>> instead of --host=${host_alias} --target=${target_alias}
>>
>> This "breaks" config.cache if used across directories, because the platforms
>> change.
>
> The reason why it is configured with none is so that it can be
> transfered to more computers than your own.
>
> -- Pinski
