-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I don't know which thread you are referring to, but maybe it was one of
> mine.
Sorry. This question from Lutz Schönemann was refered (at bottom). i
wanted to point out, that setting BUILD_* like in
BUILD_CC="i686-pc-linux-gnu-gcc"
BUILD_CXX="i686-pc-linux-gnu-g++"
BUILD_CFLAGS="-O2 -march=athlon-xp -pipe"
BUILD_CXXFLAGS=${BUILD_CFLAGS}
to build-machine specific flags solved the problem with the
machine-specifc parameters (march) for me.
portage seems not to care for build/target specific CFLAGS, but most
configures do, so exporting this variables in the shell enables some
packages to build (especiallly those, that build build-machine binaries,
like the locals-compiler in glibc)
harald
>> - Using crossdev:
>> The crossdev script worked fine and installed the whole toolchain
>> (stage4: binutils, gcc, linux-headers, etc.). The trouble is that
>> when I want to merge a packege with this compiler (e.g.:
>> CFLAGS="-arch=i386" ROOT=/tmp/cross/ CHOST=i386-unknown-linux-gnu
>> emerge sys-boot/syslinux) it ends up with the message that the
>> compiler is unable to build executables.
>Just in case that wasn't a typo in transcription - you need
>CFLAGS="-march=i386" (with an 'm'). You should look at the config.log
>etc to find out exactly why the compiler couldn't build executables.
>BTW again just in case - if your host is an x86 system,
>you don't need a
>cross-compiler as your host compiler can build for all x86 variants -
>it's enough to get the CFLAGS right; e.g.
>CFLAGS="-march=i386" ROOT=/tmp/cross emerge <pkg>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFESNDIJgyxs71kcx4RAgPkAJ433wMAObmRQo5qarx1kjzyz+sbFgCeLE2v
XECMbsoIVkxeomlLn7wsJjU=
=kBVJ
-----END PGP SIGNATURE-----
--
[email protected] mailing list
