Bug#797917: Actually this bug makes clang not so useful

Hi Danny, >$ g++ -std=c++98 -o options options.cpp -lboost_program_options >$ clang++ -std=c++98 -o options options.cpp -lboost_program_options the fact is that even if your code is not directly using c++11 symbols, the underlying libraries (boost_program_options in this case) are, so you

Bug#797917: Actually this bug makes clang not so useful

On 04/09/15 11:23, Gianfranco Costamagna wrote: > > I guess clang is not useful for cxx11 projects until llvm folks finds > a way to make it use the new ABI. > Hi everyone, I just want to make clear that this is *not* specific to c++11 projects. Even if you don't use any c++11 features, clang

Bug#797917: Actually this bug makes clang not so useful

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Danny, > If we could make those "Dual-ABI compile flags" the default on > gcc-compiled libraries, clang upstream should have enough time > implementing [abi:cxx11] and remain usable in Debian. gcc had the dual ABI enabled. but it got

Bug#797917: Actually this bug makes clang not so useful

Control: reassign -1 clang-3.5 Control: retitle -1 clang should use the new CXX11_ABI Control: severity -1 serious Well this bug makes clang almost useless with the new gcc compiler. according to [1] there might be no fix. I hope somebody with more knowledge can come up with a fix,

Bug#797917: Actually this bug makes clang not so useful

On Thu, 3 Sep 2015 17:45:27 + (UTC) Gianfranco Costamagna wrote: > according to [1] there might be no fix. > This may not be a permanent fix, but Debian could take up the "dual-abi" idea that gcc upstream does with their libstdc++.so.6. Example: $ nm -D