boost @ 1.70.0_0+no_single+no_static+python27+universal fails to build

[gverm (Gijs Vermeulen)]

I'm running High Sierra on 2015 MacBook Pro, Xcode 9.
Log is attached.

[gverm (Gijs Vermeulen)]

log

[ryandesign (Ryan Carsten Schmidt)]

I have the same problem on my system. It's probably specific to using the universal variant; if you can do without that, that should fix it.

:info:build ld: warning: ignoring file bin.v2/libs/container/build/darwin-4.2.1/release/address-model-32_64/pch-off/threading-multi/visibility-hidden/alloc_lib.o, file was built for x86_64 which is not the architecture being linked (i386): bin.v2/libs/container/build/darwin-4.2.1/release/address-model-32_64/pch-off/threading-multi/visibility-hidden/alloc_lib.o

I don't know how to fix this and am not looking into it. Help is welcome.

[kencu (Ken)]

It looks like, at least here, the arch flags are being passed to the "c++" builds (603) but not to the "c" builds (605).

603	:info:build     "/usr/bin/clang++"   -fvisibility-inlines-hidden -Os -std=gnu++11 -stdlib=libc++ -arch x86_64 -arch i386 -stdlib=libc++ -fPIC -O3 -Wall -fvisibility=hidden -dynamic -gdwarf-2 -fexceptions -Wno-inline  -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTAINER_DYN_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/container/build/darwin-4.2.1/release/address-model-32_64/pch-off/threading-multi/visibility-hidden/pool_resource.o" "libs/container/src/pool_resource.cpp"

605	:info:build     "/usr/bin/clang++" -x c                                                                                                 -fPIC -O3 -Wall -fvisibility=hidden -dynamic -gdwarf-2 -fexceptions -Wno-inline  -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTAINER_DYN_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/container/build/darwin-4.2.1/release/address-model-32_64/pch-off/threading-multi/visibility-hidden/alloc_lib.o" "libs/container/src/alloc_lib.c"

[ryandesign (Ryan Carsten Schmidt)]

This kind of thing has been a problem with boost before. I remember we had a similar problem with a previous version of boost and were able to fix it somehow, but I haven't tried to look up the details.

[michaelld (Michael Dickens)]

Yeah we've had the same issue with Boost in the past. Not enough time or desire to fix it. And now that new OSX doesn't natively do +universal I'm even less inclined to look into it. Maybe @kencu has the motivation?

[kencu (Ken)]

see 55857. There are fixes there that look similar.

[kencu (Ken)]

specifically <​https://github.com/ccorn/macports-ports/commit/f2867d6d55d057f4a36cfbedbc18d53a39f8682c>

[michaelld (Michael Dickens)]

oh ... that's a nice easy fix if it works!

@kencu: Can you test / verify that change? I'm on travel with a Mojave laptop so I can't test it out until next week.

[kencu (Ken)]

That patch fixes the "c" builds, but then there are still a few "asm" files that need fixing up with arch flags as well, and that seems a bit harder to force as there don't seem to be any <asmflags> at least so far...

[kencu (Ken)]

Oh yes there are <asmflags>! Isn't that handy... tweaking...

[kencu (Ken)]

In b11faed22522e827899f5c54e9187031ddbd592b/macports-ports (master):

boost: add asm and cflags to build

this passes the arch flags needed to enable +universal
closes: #58846
see: #55857

[michaelld (Michael Dickens)]

Thanks @kencu!