On Tue, Aug 30, 2005 at 06:44:40PM -0700, Russ Allbery wrote: > Marc Singer <elf@xxxxxxxxx> writes: > > On Tue, Aug 30, 2005 at 08:05:30PM -0500, Bob Friesenhahn wrote: > > >> It is most likely that a libtool .la file on the system includes > >> mention of /usr/lib/libstdc++.la. That would explain the problem. > > > That's what I've been looking for. I *have* seen sub-libraries within > > the package with this reference. Still looking. > > At one time at least, libtool had a bug/misfeature where it would search > the entire library path for a *.la file and, only when it didn't find one, > go back and do a search for a regular library. Could that code still be > in place and could you be running into it? That's what it looks like is happening. I've enabled --debug and, in fact, that's what I've seen. I don't know if I can use a different version of libtool. I thought that I was using the newest already. I'm going to post to the libtool list to see if I can get more info. > > -- > Russ Allbery (rra@xxxxxxxxxxxx) <http://www.eyrie.org/~eagle/> > > > _______________________________________________ > Autoconf mailing list > Autoconf@xxxxxxx > http://lists.gnu.org/mailman/listinfo/autoconf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
