On 2018-04-25, at 11:38 AM, Riccardo Mottola wrote: > Hi,
> Forcing clang-3.4 brings up this: > > /opt/local/bin/clang++-mp-3.4 -DHAVE_CONFIG_H -I. > -I./TECkit-src/source/Public-headers -DNDEBUG -isystem/opt/local/include > -pipe -Os -std=c++11 -Wno-reserved-user-defined-literal > -D_GLIBCXX_USE_CXX11_ABI=0 -stdlib=macports-libstdc++ -arch i386 -MT > TECkit-src/source/UnicodeNames.o -MD -MP -MF $depbase.Tpo -c -o > TECkit-src/source/UnicodeNames.o TECkit-src/source/UnicodeNames.cpp &&\ > mv -f $depbase.Tpo $depbase.Po > clang: error: invalid library name in argument '-stdlib=macports-libstdc++' > clang: error: invalid library name in argument '-stdlib=macports-libstdc++' > make[5]: *** [TECkit-src/source/UnicodeNames.o] Error 1 > make[5]: *** Waiting for unfinished jobs.... > make[5]: *** [TECkit-src/source/Compiler.o] Error 1 > make[5]: Leaving directory `/opt/local/var/macports/build/ Oh, yes, I saw that too now that you mention it. > '-stdlib=macports-libstdc++ is a rather fancy MacPorts-only addition to clang 3.9+ that allows fancy footwork with the c++ standard library. It gets added by the cxx11 PortGroup. For that to work, you need clang-3.9. (although I have it working with clang-3.8 myself, on PPC no less -- but that is another story). > > Perhaps that is why you selected gcc6, due to libstdc++ > Should I try installing clang 3.9, if it it works on 10.5? clang-3.9 does work on 10.5, and works very well for me. Ken
