> Find out what the path for libstdc++.so is for the one you want,
> then set LDFLAGS=-L/correct/path/ when you build the library that it's complaining about.
> Note that it may not be PCRE, but it could be something that PCRE links to.
> Use "ldd" or "ldd -s" to find out which libraries are pulling in libstdc++ and from where.
I think that the situation is that when linking with the C++ compiler,
the C++ compiler automatically adds linkage to its own libstdc++.so.
Libtool also adds linkage to libstdc++.so (as a dependency) so the
linker sees the (hopefully) same shared library listed twice. There
would be a severe problem if libtool was to request linking with a
different libstdc++.so than the C++ compiler needs.
Solaris ld warns about this issue, and presumably GNU ld does not.