Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: boost fails to build on MIPS
Date: Fri, 29 May 2015 23:09:45 +0100	[thread overview]
Message-ID: <1432937385.2461.36.camel@pbcl.net> (raw)
In-Reply-To: <5568AEC2.7090606@topic.nl>

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

p.




  reply	other threads:[~2015-05-29 22:09 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 [this message]
2015-05-30 16:45   ` Mike Looijmans
2015-06-01  6:17     ` Robert Yang

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=1432937385.2461.36.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.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