[cfe-dev] libc++abi on linux
Ben Pope
benpope81 at gmail.com
Wed Jul 11 20:53:54 PDT 2012
On Monday, July 09, 2012 04:40 PM, David Chisnall wrote:
> On 9 Jul 2012, at 04:00, Ben Pope wrote:
>
>> clang++ -std=c++11 -stdlib=libc++ -stdlibabi=libc++abi -stdlibunwind?=???
>
> Unlike the STL implementation, the ABI and unwind libraries are per-binary. Generally, the STL implementation will pick one, so you don't need to explicitly specify either unless you are linking the STL implementation itself.
Right, but when I build the STL library, I need to specify which ABI
library it's going to use, and when I build the ABI library I need to
specify which unwind it's going to use, right?
>> What does the rest of LLVM/clang community use?
>
> In FreeBSD 9.1 (entering beta right about now), we are shipping libstdc++ and libc++, with libstdc++ linked against either libsupc++ or libcxxrt and libc++ linked against libc++. This is a preview release of libc++, so to mix it with libstdc++ in the same executable you need to add a libmap.conf entry telling libstdc++ to pick up libcxxrt instead of libsupc++. In 10.0, we will provide a libstdc++ linked to libcxxrt for legacy compatibility.
>
> All that users need to do is specify -stdlib=libc++. This will be the default on 10.0, and probably be the default when -std=c++11 before then.
Can you tell me what the output of ldd libc++.so.1 is?
Cheers.
Ben
More information about the cfe-dev
mailing list