[oe] [PATCH 0/3] Make multi-machine toolchains to co-exist.

Richard Purdie rpurdie at rpsys.net
Sun Jul 25 15:53:56 UTC 2010


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...

Cheers,

Richard





More information about the Openembedded-devel mailing list