[cfe-dev] Why no Debian package for libc++?

Arji Cot arjicot at gmail.com
Sun Jul 28 23:55:46 PDT 2013


Those are dynamically linked libraries, for what you know you could have
libsupc++ statically linked to your libc++/abi or to at least of those
libraries.

I'm not aware of any linux distribution or libc++ build under linux that is
just using libc++ without libstdc++ or libsupc++, for what I know, at this
point in time, libc++, at least under linux, is using libstdc++ and
libsupc++ to provide a complete C++ support and filling the blanks that are
still not supported by the library.

I think that libc++ will reach the indendpence from the GNU libs if and
only if it will provide a complete C++ environment.

2013/7/29 Ben Pope <benpope81 at gmail.com>

> On 27/07/13 08:17, Arji Cot wrote:
> > The errors are probably caused by the fact that you need ( and you are
> not
> > providing it to the linker ) libcxxabi http://libcxxabi.llvm.org/ .
> >
> > In general terms I personally consider both libcxx and libcxxabi under
> > Linux pretty useless right now.
> >
> > The main issues are:
> >  - libcxx and libcxxabi are simply not ready yet for Linux, they are just
> > incomplete and without a real support from the llvm project
> >  - in the end libcxx and libcxxabi will use libsupc++ and stdlibc++
> anyway,
> > so there is no point in using them, you are just introducing a new
> > dependence for nothing
>
> I've built libc++ against libc++abi on Ubuntu 13.04, and yes, you do
> need to specify -lc++ -lc++abi
>
> ben at localhost:/usr/lib$ ldd libc++.so
>         linux-vdso.so.1
>         libc++abi.so.1
>         libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
>         libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
>         librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1
>         libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
>         /lib64/ld-linux-x86-64.so.2
> ben at localhost:/usr/lib$ ldd libc++abi.so
>         linux-vdso.so.1
>         libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>         librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1
>         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
>         libc++.so.1 => /usr/lib/libc++.so.1
>         /lib64/ld-linux-x86-64.so.2
>         libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
>         libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
>
> libsupc++ is not required if libc++abi is used, and of course, libstdc++
> is also not required.
>
> In this configuration, with Clang 3.3, the llvm nightly test suite
> passes. (Ok, there is one failure, but it's the same as with libstdc++)
>
> Ben
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130729/8550cc08/attachment.html>


More information about the cfe-dev mailing list