[OE-core] [PATCH] jpeg-native: Do not use libtool-cross for native recipe

Khem Raj raj.khem at gmail.com
Thu Sep 27 15:44:00 UTC 2012


On Thu, Sep 27, 2012 at 8:16 AM, Richard Purdie
<richard.purdie at linuxfoundation.org> wrote:
> On Thu, 2012-09-27 at 07:14 -0700, Khem Raj wrote:
>> On Wed, Sep 26, 2012 at 6:59 AM, Richard Purdie
>> <richard.purdie at linuxfoundation.org> wrote:
>> > On Tue, 2012-09-25 at 06:27 -0700, Khem Raj wrote:
>> >> On Tue, Sep 25, 2012 at 1:14 AM, Richard Purdie
>> >> <richard.purdie at linuxfoundation.org> wrote:
>> >> > This wallpapers over cracks. Why is libtool-native/libtool-cross broken?
>> >> > Shouldn't we fix whatever is breaking libtool?
>> >> >
>> >>
>> >> it is not broken. But we were ending up using cross-libtool for native
>> >> recipe that does not seem right.
>> >
>> > Looking at your original error message, it says:
>> >
>> >  /work/yocto/poky/build/tmp/sysroots/x86_64-linux/usr/bin/x86_64-linux-libtool
>> >
>> > which is libtool-native. I appreciate that the OEMAKE line to use the
>> > cross version is wrong but it looks like it still manages to find the
>> > native libtool and that it isn't working.
>>
>> hmmm I tried and it worked fine when libtool-cross was staged. I guess
>> my problem was
>> that it was trying to find native sed in native sysroot. I cant
>> reproduce it. But I guess
>> the patch still makes sense. I can send it with commit message changed
>> if you are ok with that
>
> I'm not really. I'd like to understand what the problem is we're fixing
> before I take patches. We don't understand what is wrong here.
>


yes it seems something else is going on since for native recipes
STAGING_BINDIR_CROSS=${STAGING_BINDIR_NATIVE}
which means it ends up sourcing the native libtool for jpeg-native

When I did bitbake jpeg-native from scratch it worked fine too.

It appeared on a build server so it could have some weird race condition show
up. I will keep an eye if it happens again then I would like to
understand and hopefully reproduce.

Let me withdraw this patch.

> Cheers,
>
> Richard
>




More information about the Openembedded-core mailing list