On 11/22/2011 11:36 PM, Adam Mercer wrote:
On Mon, Nov 21, 2011 at 15:39, Peter O'Gormanpe...@pogma.com wrote:
Glad it works around it. The problem is libtool brokenness, most vendors
patch around it in their packaged libtool, e.g.
On Wed, Nov 23, 2011 at 08:52, Peter O'Gorman pe...@pogma.com wrote:
I'm not sure if we ever looked for what distros use what layout for
multilibs, and how to detect them.
There was a patch somewere which was slow, but ended up correct, using
ldconfig. I'll look for it again.
Thanks, let me
On Mon, Nov 21, 2011 at 15:39, Peter O'Gorman pe...@pogma.com wrote:
Glad it works around it. The problem is libtool brokenness, most vendors
patch around it in their packaged libtool, e.g.
Hi,
On 11/19/2011 01:03 AM, Adam Mercer wrote:
Hi
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
On Mon, Nov 21, 2011 at 12:21, Peter O'Gorman pe...@pogma.com wrote:
Peter
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
makefile.am, please?
I am not setting these myself and they don't seem to
On 11/21/2011 03:22 PM, Adam Mercer wrote:
Setting lt_cv_sys_lib_dlsearch_path_spec=/lib64 /usr/lib64 at
configure time results in -Wl,-rpath -Wl,/usr/lib64 not being passed
and the correct libraries linked. So this is a workaround but I'd like
to understand why these flags are being added in
Hi
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
