[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: linking problems on SL6

From: Peter O'Gorman
Subject: Re: linking problems on SL6
Date: Mon, 21 Nov 2011 12:21:20 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110906 Fedora/3.1.14-1.fc14 Thunderbird/3.1.14


On 11/19/2011 01:03 AM, Adam Mercer wrote:

In building a development snapshot of one of my projects, to a custom
path, on SL6 I am running into what appears to be a linking problem.
The libtool command used to link the library is as follows:

libtool: link: gcc -std=gnu99 -shared  -fPIC -DPIC .libs/Aggregation.o
.libs/FrameCache.o .libs/FrameCalibration.o .libs/FrameData.o
.libs/FrameSeries.o .libs/FrameStream.o .libs/LALFrameIO.o
.libs/LALFrameVCSInfo.o .libs/LowLatencyData.o -Wl,-rpath
-Wl,/usr/lib64 -Wl,-rpath
-Wl,/usr1/ram/lalsuite/lal/packages/support/src/.libs -Wl,-rpath
-Wl,/usr1/ram/lalsuite/lal/lib/.libs -Wl,-rpath -Wl,/usr/lib64
-Wl,-rpath -Wl,/home/ram/lalsuite/lib64 /usr/lib64/
../../lal/packages/support/src/.libs/ -lz
../../lal/lib/.libs/ -lgsl -lgslcblas -lfftw3 -lfftw3f -lm
-O2   -Wl,-soname -Wl, -o .libs/

Are these -Wl,-rpath flags coming from libtool? They seem to be there already on the libtool command line. Could you post this snippet of your, please?

The problem is that there is the current release version, installed
from the release RPM, in /usr and because of the "-Wl,-rpath
-Wl,/usr/lib64" on the link line this older version is getting picked
up in preference to the more recent development version in
/home/ram/lalsuite. Why would libtool be passing /usr/lib64 to the
compiler? On Debian Squeeze, using the same git tag, the build
succeeds so I am led to believe that this is an issue with the
autotools on SL6 but I'm not sure where to start looking. Has any got
any suggestions?

Libtool has issues with multilib systems. Someone had a patch at some point that correctly figured out the multilib library paths using ldconfig, but I've long forgotten who. You can set lt_cv_sys_lib_dlsearch_path_spec and lt_cv_sys_lib_search_path_spec at configure time if libtool is getting sys_lib_dlsearch_path_spec/sys_lib_search_path_spec wrong (check the generated libtool script for ^sys_lib_dlsearch_path_spec and ^sys_lib_search_path_spec to see what it's guessing).

Debian/Red Hat systems do multilib differently, one has lib32 and lib, the other lib and lib64, I wouldn't be surprised if someone has a linux system with lib32 lib and lib64 (like IRIX!).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]