On Fri, May 10, 2013 at 03:29:13PM +0200, Joerg Sonnenberger wrote:
Let me dig for a moment to see why the configure test doesn't fail...
So it is a combination of hacks:
- clang will translate -lstdc++ into the used STL implementation, since
that is what the user likely wanted to do, including the correct
library path. Background is that e.g. on Linux, it is often installed
outside /usr/lib and when using libc++, it would give incorrect
results.
- configure believes that it should add -lstdc++ to LIBS.
- libtool see -lstdc++, but doesn't know what to do with it, since no
corresponding library is found. Therefore it will refuse to build the
shared library.
I don't really want to add a subst rule to translated -lstdc++ into
-lc++, since the name of the library is an implementation detail. Just
commenting out the test case seems like the easiest solution by far.