* boost fails to build on MIPS
@ 2015-05-29 18:24 Mike Looijmans
2015-05-29 22:09 ` Phil Blundell
0 siblings, 1 reply; 4+ messages in thread
From: Mike Looijmans @ 2015-05-29 18:24 UTC (permalink / raw)
To: openembedded-core
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: boost fails to build on MIPS
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
0 siblings, 1 reply; 4+ messages in thread
From: Phil Blundell @ 2015-05-29 22:09 UTC (permalink / raw)
To: Mike Looijmans; +Cc: openembedded-core
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: boost fails to build on MIPS
2015-05-29 22:09 ` Phil Blundell
@ 2015-05-30 16:45 ` Mike Looijmans
2015-06-01 6:17 ` Robert Yang
0 siblings, 1 reply; 4+ messages in thread
From: Mike Looijmans @ 2015-05-30 16:45 UTC (permalink / raw)
To: Phil Blundell; +Cc: openembedded-core
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?
--
Mike Looijmans
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: boost fails to build on MIPS
2015-05-30 16:45 ` Mike Looijmans
@ 2015-06-01 6:17 ` Robert Yang
0 siblings, 0 replies; 4+ messages in thread
From: Robert Yang @ 2015-06-01 6:17 UTC (permalink / raw)
To: Mike Looijmans, Phil Blundell; +Cc: openembedded-core
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
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-06-01 6:17 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox