Re: [gentoo-embedded] CBUILD= HOSTCC=-gcc

[Christoph Spielmann <spielc@gmail.com>]

Am 04.01.2011 20:47, schrieb wireless:
> On 01/03/11 16:11, Christoph Spielmann wrote:
>
>> Well in terms of crossdev i686-gentoo-linux-gnu-gcc is not a valid
>> target (just look at the output of crossdev --help). If you want to
>> build x86-code on a machine using a x86-compiler why would you want to
>> use a cross-compilation-environment anyway? The idea of using
>> cross-compilation is to build stuff for another target than the target
>> of the host-compiler... E.g. build arm-code on a x86-machine or compile
>> stuff for ppc on a x86-64-machine.
>
> OK I agree with this answer, mostly.
>
> I have a situation where a x86 (P4) Machine is built on i686 for
> everything. However, I'm also going to chroot the machine and build
> binaries for all sorts of i486/586 and old oddball processors such as
> the Geode.
>
> So isn't that a valid exception to what you have opined about?

Okey but all these things are in the end x86-processors. Some support 
flags that other's won't but in the end they are basically all the same 
arch. So my suggestion would've been: use a chroot-environment for such 
a case.

In my eyes it only makes sense to use cross-compilation (including all 
the hassles that you will come across by using it) if you need (or want) 
to build stuff for another architecture or machine, that is not 
powerfull enough for compilation tasks itself. E.g. arm5-code on a 
x86_64-environment

>
> curious,
> James
>
>
>