On Fri, Jul 28, 2017 at 06:50:35AM +0200, Sebastien Marie wrote: > Hi, > > I would like to understand the rationale about the addition of > COMPILER_LIBCXX in WANTLIB on lang/rust. > > lang/rust is compiled using ports gcc4.9. The c++ library used is > libestdc++. And the use of devel/llvm is due linkage with LLVM libraries > (base isn't suitable for that: we don't have libLLVM*.so but only > clang/clang++). > > Previously, the WANTLIB for main was: > > rust-1.18.0$ make show=WANTLIB-main > estdc++>=17 c m pthread z > > > Now, the WANTLIB-main has c++ and c++abi added, and estdc++ is missing:
Yes, that's definitely not matching what rust does. Sthen, you probably want to revert that one, rust *does* want gcc4 from ports currently. (the fact it's still using MODULES = gcc4 directly is a tell-tale) Semarie, on the other hand, on a clang-based architecture, rust is now very much on its own. libstdc++ is wildy incompatible with libc++, which basically means that you can build rust programs, but you can't link with other C++ based software, and vice-versa.
