Boost libs built as x86 library with qemumips target

Boost libs built as x86 library with qemumips target

[Pete Couperus]

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

Hello,

I'm new to poky, and was trying to build 'poky-image-minimal' for a couple
of targets.
After success with 'poky-image-minimal' for qemux86, I tried out the
qemumips target.
Things seemed to be going fine, until it errored out trying to build libzypp
with a bunch
of:
skipping incompatible
/home/twocog/poky-builds/build-mips/tmp/sysroots/mips-poky-linux/usr/lib/libboost_signals-mt.so
when searching for -lboost_signals-mt.
Indeed, file libboost_signals.so.1.44.0 reports ELF x86, where all of the
other
.so in this directory are ELF mips.
On looking at the boost build artifacts, they all seem to be x86.
The host machine is x86.
This is using poky-laverne-4.0.
Any help/guidance would be appreciated, I realize there are many moving
pieces here.  I can provide more diagnostics if needed.
Thanks.

Pete

[-- Attachment #2: Type: text/html, Size: 898 bytes --]

Re: Boost libs built as x86 library with qemumips target

[Darren Hart]

On 03/27/2011 08:28 PM, Pete Couperus wrote:
> Hello,
>
> I'm new to poky, and was trying to build 'poky-image-minimal' for a
> couple of targets.
> After success with 'poky-image-minimal' for qemux86, I tried out the
> qemumips target.
> Things seemed to be going fine, until it errored out trying to build
> libzypp with a bunch
> of:
> skipping incompatible
> /home/twocog/poky-builds/build-mips/tmp/sysroots/mips-poky-linux/usr/lib/libboost_signals-mt.so
> when searching for -lboost_signals-mt.
> Indeed, file libboost_signals.so.1.44.0 reports ELF x86, where all of
> the other
> .so in this directory are ELF mips.
> On looking at the boost build artifacts, they all seem to be x86.
> The host machine is x86.
> This is using poky-laverne-4.0.
> Any help/guidance would be appreciated, I realize there are many moving
> pieces here.  I can provide more diagnostics if needed.
> Thanks.

I'm taking a stab at this since others haven't responded yet. Sounds 
like a bad reuse of sstate (not sure if that's available in your 
version) or host contamination.

Can you try:

$ bitbake -c clean -f libboost (for each of the boost recipes)

to be safe remove sstate-cache/*libboost* and then try building again. 
Does the problem persist?

--
Darren

>
> Pete
>
>
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel