From: Mike Looijmans <mike.looijmans@topic.nl>
To: openembedded-core@lists.openembedded.org
Subject: boost fails to build on MIPS
Date: Fri, 29 May 2015 20:24:02 +0200 [thread overview]
Message-ID: <5568AEC2.7090606@topic.nl> (raw)
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?
For example:
| gcc.compile.c++
bin.v2/libs/atomic/build/gcc-4.3.1/release/threading-multi/lockpool.o
| mipsel-oe-linux-g++: error: unrecognized command line option '-m32'
|
| "mipsel-oe-linux-g++" "-mel" "-mabi=32" "-mhard-float"
"-march=mips32" "-Wl,-O1" "-Wl,--as-needed"
"--sysroot=/home/milo/work/openpli-next/build/tmp/sysroots/vuduo2"
-ftemplate-depth-128 -Os -pipe -g -feliminate-unused-debug-types
-fvisibility-inlines-hidden -O3 -finline-functions -Wno-inline -Wall
-pthread -fPIC -m32 -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1
-DBOOST_ATOMIC_SOURCE -DNDEBUG -I"." -c -o
"bin.v2/libs/atomic/build/gcc-4.3.1/release/threading-multi/lockpool.o"
"libs/atomic/src/lockpool.cpp"
--
Mike Looijmans
next reply other threads:[~2015-05-29 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 18:24 Mike Looijmans [this message]
2015-05-29 22:09 ` boost fails to build on MIPS Phil Blundell
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=5568AEC2.7090606@topic.nl \
--to=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