From: Robert Yang <liezhi.yang@windriver.com>
To: Mike Looijmans <mike.looijmans@topic.nl>, Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: boost fails to build on MIPS
Date: Mon, 1 Jun 2015 14:17:25 +0800 [thread overview]
Message-ID: <556BF8F5.5030906@windriver.com> (raw)
In-Reply-To: <5569E91D.8070104@topic.nl>
On 05/31/2015 12:45 AM, Mike Looijmans wrote:
> On 30-05-15 00:09, Phil Blundell wrote:
>> On Fri, 2015-05-29 at 20:24 +0200, Mike Looijmans wrote:
>>> On current OE master, boost fails to build, because something attempts
>>> to add "-m32" to the gcc commandline for no apparent reason.
>>>
>>> Can anyone confirm this, or am I the only MIPS user in the world?
>>
>> This is an upstream boost bug. See the entertaining history at:
>>
>> https://github.com/boostorg/build/commit/9576ca216cae888d7efb5da97c009c245c5ba567
>
> Strange, I added this fix as a patch to bjam (which seems to be the one causing
> all the troubles), but still get the same build error, even after cleansstate
> both bjam-native and boost.
>
> Maybe some cross-compiler stupidity like that it looks at the build machine's
> arch instead of the target host's?
Hello,
I verified the following 2 patches work:
https://github.com/boostorg/build/commit/c0634341d9ee2c02d3a55c91dafb988afc066c49
https://github.com/boostorg/build/commit/9576ca216cae888d7efb5da97c009c245c5ba567
I will send a fix for boost.
// Robert
>
>
>
prev parent reply other threads:[~2015-06-01 6:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 18:24 boost fails to build on MIPS Mike Looijmans
2015-05-29 22:09 ` Phil Blundell
2015-05-30 16:45 ` Mike Looijmans
2015-06-01 6:17 ` Robert Yang [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=556BF8F5.5030906@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.