[oe] [PATCH][v4] Make multi-machine toolchains to co-exist (revised again)

Khem Raj raj.khem at gmail.com
Sun Aug 1 08:14:57 UTC 2010


On Sat, Jul 31, 2010 at 3:59 PM, Richard Purdie <rpurdie at rpsys.net> wrote:
> On Thu, 2010-07-29 at 23:36 -0700, Khem Raj wrote:
>> On Thu, Jul 29, 2010 at 7:52 PM, Tom Rini <tom_rini at mentor.com> wrote:
>> > Hey all,
>> >
>> > As one of the folks who suggested something else, here's my take.
>> >
>> > We modify the prefix for cross stuff to dump everything into
>> > MULTIMACH_TARGET_SYS in the sysroot.
>> >
>> > Pro: It should work for all the cases
>> > Con: We're back to having a 'special' directory of cross stuff
>> > Pro: It's separate but still valid for $ORIGIN mangling, which is the
>> > other problem we had before.
>> >
>> > I've got a qemuarm console-image and then beagleboard console-image build
>> > going now and that's going to take time.
>> >
>> > Signed-off-by: Tom Rini <tom_rini at mentor.com>
>>
>> hah indecently I have been testing similar patch per our discussions on IRC
>> but trying to get program-transform-name to generate unique compiler names
>> which can coexist in <native sysroot>/usr/bin meanwhile I work on that this
>> portion looks ok to go in.
>>
>> Signed-off-by: Khem Raj <raj.khem at gmail.com>
>
> I've been trying to catch up with this issue and where OE is at now I'm
> back. Could someone summarise where we're at please as reading through
> the email threads which keep changing subject hasn't really educated me
> much :/ Did changing the triplet work out or not?

Yes it worked out to a certain extent but there was few rough edges left. I did
not pursue it more as it seemed not so desired approach.

>
> In Poky I've got the putting the toolchain into:
>
> native-sysroot/usr/bin/<package-triplet>/${TARGET_SYS}-foo

Something similar is what the v4 of the patch proposed. A difference is
that it puts the toolchain in native-sysroot/usr/${BASE_PACKAGE_ARCH}/

Koen has been trying it out and so far he has had good results.

Thanks
-Khem




More information about the Openembedded-devel mailing list