[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
libtool/ltmain.sh pulling in wrong stdc++
From: |
Graham Leggett |
Subject: |
libtool/ltmain.sh pulling in wrong stdc++ |
Date: |
Wed, 3 Aug 2005 13:57:20 +0200 (SAST) |
User-agent: |
SquirrelMail/1.4.3a-9.EL4 |
Hi all,
I have been having a very strange problem that I have tracked down to
libtool, and I don't know how to proceed.
I have a Solaris v2.8 machine with a system installed copy of gcc v3.4.2
in /usr/local. Recently a private copy of gcc v4.0.1 was installed in a
private directory. The private directory appears first in both PATH and
LD_LIBRARY_PATH.
I have a project containing C++ code. When this project is built using
configure and libtool, an attempt is made to pull in the system stdc++
within /usr/local, and not the stdc++ within the private directory, even
though the private gcc and g++ are both in the path and take precedance:
bash-2.03$ g++ --version
g++ (GCC) 4.0.1
What method needs to be used to tell libtool to link to stdc++ that
belongs to the compiler being run?
How does ltmain.sh find libraries to create the dependancy_libs variable?
Regards,
Graham
--
- libtool/ltmain.sh pulling in wrong stdc++,
Graham Leggett <=