[OE-core] Specifying 32 bit dependency for 64 bit software

Laszlo Papp lpapp at kde.org
Mon Jan 5 12:48:12 UTC 2015


On Thu, Nov 20, 2014 at 6:17 PM, Laszlo Papp <lpapp at kde.org> wrote:
> On Tue, Nov 4, 2014 at 11:48 AM, Richard Purdie
> <richard.purdie at linuxfoundation.org> wrote:
>> On Mon, 2014-11-03 at 17:29 +0000, Laszlo Papp wrote:
>>> we have a tool that we run during our make run, but this tool is
>>> hard-coded for 32 bit. It depends on software like ncurses. I could
>>> add ncurses-native in an ideal world; no problem.
>>>
>>> The problem is that my host environment is 64 bit currently and it is
>>> not possible to migrate the whole environment to 32 bit. I am happy to
>>> explain the details if needed, but I would love you to trust me about
>>> that. =)
>>>
>>> So, is it possible to say more than just DEPENDS = ncurses-native,
>>> something like DEPENDS = ncurses-native:x86 or something?
>>
>> How much of a 32 bit system do you have? Do you at least have a 32 bit
>> capable compiler and C libraries?
>>
>> If so, you could use our general class extension mechanism
>> (BBCLASSEXTEND) to allow 32 bit variants of the native recipes, e.g. a
>> "native32" form.
>>
>> Alternatively, a more easier approach would be to build a target like
>> buildtools-tarball with SDKMACHINE="i686" and then install that onto the
>> system you're building on.
>
> I am just back from my long vacation. I am sorry about not replying
> earlier. OK, thank you so much; I will give the buildtools-tarball a
> go.

In the end, it was simpler to use this on my Wheezy (Debian)

dpkg --add-architecture i386 && apt-get update && apt-get install
install mylib:i386

>
> Cheers, L.
>
>>
>> Cheers,
>>
>> Richard
>>
>>
>>
>>
>>



More information about the Openembedded-core mailing list