Boost logo

Boost :

Subject: Re: [boost] [release] Boost 1.64.0 Beta 1
From: Deniz Bahadir (dbahadir_at_[hidden])
Date: 2017-03-27 12:32:28

Am 27.03.2017 um 13:00 schrieb John Maddock via Boost:
>> Oh, and I forget to mention another observation:
>> Why does the configuration summary state that Clang 3.8 does not
>> support the "visibility" feature? I think that is just wrong.
>> The configuration summary for Clang 3.8 looks like the following.
>> (Except for the "visibility" feature it is the same for GCC 4.8 and
>> GCC 6.)
> If you look in bin.v2/config.log you will see the error messages from
> the failed test - ie the reason it was disabled.

Thanks, John, that helped.

Clang did not like my linker-input, because it was only trying to
compile not link:

...updated 5 targets...
...found 6 targets...
...updating 5 targets...
clang: error: -lc++abi: 'linker' input unused
clang: error: -lc++abi: 'linker' input unused

   "clang++" -c -x c++ -fvisibility=hidden -m64 -fpic
-fdiagnostics-color=always -std=c++14 -stdlib=libc++
-isystem/usr/include/libcxxabi -lc++abi -O0 -Werror -g -m64 -fpic
-fdiagnostics-color=always -fno-inline -Wall -pedantic -Werror -g
-fPIC -m64 -fvisibility=hidden -m64 -fpic -fdiagnostics-color=always
-std=c++14 -stdlib=libc++ -isystem/usr/include/libcxxabi -lc++abi -m64
-fpic -fdiagnostics-color=always -DBOOST_ALL_NO_LIB=1 -I"." -o

...failed clang-linux.compile.c++.without-pth
...failed updating 1 target...

It seems, I should not add a link-flag like "-lc++abi" to Boost.Build
option "cxxflags!? Should I only use Boost.Build option "linkflags" or
would I additionally have to prepend a "-Wl," to that link-flag?


> HTH, John.

Boost list run by bdawes at, gregod at, cpdaniel at, john at