libc++ vs. libstdc++ usage in the ports tree (was: Re: Are clang++ and libc++ compatible?)

2013-11-13 Thread Marcus von Appen
Steve Kargl s...@troutmask.apl.washington.edu: [...] Sigh. Adding USE_GCC isn't the solution. % pan Segmentation fault (core dumped) % ldd /usr/local/bin/pan | grep ++ libstdc++.so.6 = /usr/local/lib/gcc46/libstdc++.so.6 (0x3c52bf000) libc++.so.1 = /usr/lib/libc++.so.1

Re: libc++ vs. libstdc++ usage in the ports tree (was: Re: Are clang++ and libc++ compatible?)

2013-11-13 Thread Andreas Nilsson
https://wiki.freebsd.org/NewC++Stack says things about linking against both libc++ and libstdc++ , do they still apply? Best regards Andreas ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: libc++ vs. libstdc++ usage in the ports tree (was: Re: Are clang++ and libc++ compatible?)

2013-11-13 Thread Ryan Stone
On Wed, Nov 13, 2013 at 11:31 AM, Marcus von Appen m...@freebsd.org wrote: This brings up another point into which I am running with the previously discussed blender issue. Let's assume port A_defcompiler does not specify a compiler and c++ lib, it will default to libc++ and clang++ on 10.x

Re: libc++ vs. libstdc++ usage in the ports tree (was: Re: Are clang++ and libc++ compatible?)

2013-11-13 Thread Steve Kargl
On Wed, Nov 13, 2013 at 12:52:16PM -0500, Ryan Stone wrote: On Wed, Nov 13, 2013 at 11:31 AM, Marcus von Appen m...@freebsd.org wrote: This brings up another point into which I am running with the previously discussed blender issue. Let's assume port A_defcompiler does not specify a