-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25-07-10 21:43, Khem Raj wrote: > On Sun, Jul 25, 2010 at 8:53 AM, Richard Purdie <[email protected]> wrote: >> On Sun, 2010-07-25 at 17:10 +0200, Koen Kooi wrote: >>>> And cacao: >>>> >>>> | configure: error: armv7a systems are not supported at this time >>>> | ERROR: Function do_configure failed >>>> >>>>> yes I was expecting that kind of problems. openssl also has similar >>>>> issues. >>>> >>>>> another idea that struck me was that we could change the target triplet >>>>> to drop >>>>> TARGET_VENDOR and replace it with TARGET_SUB_ARCH and TARGET_SUBARCH >>>>> could be anything >>>>> we could even make it same as MACHINE_ARCH which means you will build >>>>> toolchain per machine >>>>> and they will live together. >>>> >>>>> then the tool names will be something like arm-v7-linux-gnueabi-* >>>>> powerpc-e500-linux-gnu >>>>> mips-mips2-linux etc. instead of *-angstrom-*- or *-oe-*- >>>> >>>>> or arm-beagleboad-linux-gnueabi-* etc if we go with MACHINE_ARCH >>>> >>>>> that would keep all recipe configury happy as the arch detected from >>>>> config.guess will be what >>>>> we had (arm, mips, mipsel powerpc etc) so no changes needed but we >>>>> will have to drop the brand >>>> >>>>> does it sound good ? bad? >>> >>> I don't think abusing target vendor for that is a good idea. And I'm >>> quite attached to my angstrom branded toolchains, tbh. >> >> Note that you can still append your angstrom string to the vendor part >> of the triplet... > > arm-v7_angstrom-linux-gnueabi- etc. is a possibility
that would work for me :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFMTT5KMkyGM64RGpERAiNNAJ4pWZ3QzrdsF0zioWrU1oAmTuAF8QCghWiA jYNyaUoeD+N7muCWMbilM78= =tcjx -----END PGP SIGNATURE----- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
