From: Darren Hart <dvhart@linux.intel.com>
To: Pete Couperus <pjcoup@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: Boost libs built as x86 library with qemumips target
Date: Mon, 04 Apr 2011 11:41:23 -0700 [thread overview]
Message-ID: <4D9A10D3.9000002@linux.intel.com> (raw)
In-Reply-To: <AANLkTimyMqJN4q1gnG-M9t02GdrotJD5tvxEbr--k3x2@mail.gmail.com>
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
prev parent reply other threads:[~2011-04-04 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 3:28 Boost libs built as x86 library with qemumips target Pete Couperus
2011-04-04 18:41 ` Darren Hart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D9A10D3.9000002@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=pjcoup@gmail.com \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox