On Tue, Oct 15, 2013 at 01:57:44PM +0200, Alberto Villa wrote: > On Tue, Oct 15, 2013 at 1:43 PM, Baptiste Daroussin <b...@freebsd.org> wrote: > > We have to limit the number of compilers we do support, and given the > > different > > possible options people can have: CLANG_IS_CC WITHOUT_CLANG WITHOUT_GCC it > > would > > be a nightmare to support all combinaison. > > Actually I was discussing another issue, that is: lang/clang33 doesn't > provide c++11 features, according to the attached log. I'll try > changing it to c++11-lib and see what happens, but I think c++11-lang > should be enough. Am i wrong?
Oh yes you are wrong, there is a distinction between c++11-lang and c++11-lib on purpose. Clang33 from ports and base uses libstdc++ from gcc 4.2 for all but freebsd 10. but clang33 has c++11 langague support meaning it knows how to parse c++11 keywords. But some ports requires a c++11 library may it be libstdc++ from a newer gcc or libc++, that is what c++11-lib is for. regards, Bapt
pgp0CcPeXF1y9.pgp
Description: PGP signature
_______________________________________________ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
