-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21-12-09 03:13, Khem Raj wrote: > On Sun, Dec 20, 2009 at 11:04 AM, Koen Kooi <[email protected]> wrote: >>> On Thu, 2009-12-17 at 12:07 -0800, Khem Raj wrote: >>>> >>>> * This is not supporting multilib >>>> * Only 64-bit userspace can be built. >>>> >>>> --- /dev/null >>>> +++ b/conf/machine/include/tune-x86_64.inc >>>> @@ -0,0 +1,4 @@ >>>> +TARGET_CC_ARCH = "-mtune=generic" >>>> +BASE_PACKAGE_ARCH = "x86_64" >>>> +FEED_ARCH = "x86_64" >>>> +PACKAGE_EXTRA_ARCHS += "x86 i386 i486 i586 i686" >> >> NAK! Don't use underscores in machine names since it's what bitbake is using >> to mark overrides. I fell into that trap twice already :( >> >> Also, please explain to me what you plan to do with 'FEED_ARCH'. > > I was thinking of using amd64 but ARCH has to be > x86_64 at least for gcc so I think we can not avoid > it. may be we should make bitbake ignore certain > overrides like x86_64 if thats possible at all.
We re-write arch already for kernel recipes, so why can't we do the same for gcc? regards, Koen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFLLzqAMkyGM64RGpERAtuHAJ9YxU54qCR7lAiUbjkxRqBi7ISycACeOkMG yrR9wiUNLhHC4im/yz7j92s= =Lk4J -----END PGP SIGNATURE----- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
