Ralf Wildenhues wrote:
That is only half of the problem. If it were the only problem, then we
could just prepend all the lib64 paths on GNU/Linux, and the sparcv9
ones on Solaris. The other half is that libtool does not skip libraries
it finds there: deplibs_check_method is set to pass_all.
On Fri, 31 Mar 2006, Simon Stelling wrote:
Ralf Wildenhues wrote:
That is only half of the problem. If it were the only problem, then we
could just prepend all the lib64 paths on GNU/Linux, and the sparcv9
ones on Solaris. The other half is that libtool does not skip libraries
it finds
Bob Friesenhahn wrote:
Uhm, why is that a problem? If libtool did a check which ABI it's
actually
compiling/linking for, it could always prepend the appropriate path, no?
That sounds like a good plan. Unfortunately, libtool does not appear to
check ABIs while linking. Instead it uses
On Fri, 31 Mar 2006, Simon Stelling wrote:
Bob Friesenhahn wrote:
Uhm, why is that a problem? If libtool did a check which ABI it's
actually
compiling/linking for, it could always prepend the appropriate path, no?
That sounds like a good plan. Unfortunately, libtool does not appear to
Hi Simon, Bob,
Sorry for the delay.
* Bob Friesenhahn wrote on Sun, Mar 12, 2006 at 04:53:37PM CET:
On Sat, 11 Mar 2006, Simon Stelling wrote:
It seems like libtool has some problems on multilib-enabled systems.
Yes.
When libtool is given a -l argument is tries to find a matching libtool
On Sat, 11 Mar 2006, Simon Stelling wrote:
It seems like libtool has some problems on multilib-enabled systems.
When libtool is given a -l argument is tries to find a matching libtool
archive by searching through various paths:
for searchdir in '$newlib_search_path' '$lib_search_path'
