Are the gcc folks aware of this gotcha? Bob Friesenhahn wrote: > On Fri, 27 Aug 2004, Carlo Wood wrote: > >> >> It might be that one of the libraries that you are using >> thinks that it needs it (is specifically asking for it). >> The first thing you should do is to find out which library >> thinks that it depends on /usr/local/lib/./libstdc++.so (if any). > > > The libstdc++.la file produced by GCC has been broken ever since GCC > started libtool. It includes a bunch of junk it should not. The most > annoying junk refers to the GCC build directory so that applications > linked with libstdc++.la attempt to use files from the GCC build > directory rather than the installed versions. If the GCC build > directory is not removed after installing the compiler, very strange > problems result. > > I usually see the "duplicated" library warning for libstdc++.so when > linking under Solaris.
Cheers,
Gary.
--
Gary V. Vaughan ())_. [EMAIL PROTECTED],gnu.org}
Research Scientist ( '/ http://tkd.kicks-ass.net
GNU Hacker / )= http://www.gnu.org/software/libtool
Technical Author `(_~)_ http://sources.redhat.com/autobook
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/libtool
