[Top][All Lists]

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

How does libtool decide which so to link against?

From: Giles Anderson
Subject: How does libtool decide which so to link against?
Date: Mon, 25 Oct 2010 21:12:24 +0100
User-agent: KMail/1.13.5 (Linux/; KDE/4.4.5; x86_64; ; )

I am sure this has been asked before, so apologies upfront.

I have upgraded Boost and find that I have to re-link my own executables.
Should I have to? I dont really want to.

I have these Boost.File System libraries placed:

lrwxrwxrwx. 1 gander gander     29 2010-10-22 12:41 
/home/gander/lib64/ ->      
-rwxrwxr-x. 1 gander gander 188343 2010-10-22 12:41 

and I have an executable which is being built with:

g++ -DHAVE_CONFIG_H -I. -I.  -I/home/gander/include   -Wall -O3 -m64 -mtune=k8 
-MT gadirs-gadirs.o -MD -MP -MF .deps/gadirs-gadirs.Tpo -c -o gadirs-gadirs.o 
`test -f 'gadirs.cpp' || echo './'`gadirs.cpp
mv -f .deps/gadirs-gadirs.Tpo .deps/gadirs-gadirs.Po
rm -f gadirs
/bin/sh ./libtool --tag=CXX   --mode=link g++  -Wall -O3 -m64 -mtune=k8 -
L/home/gander/lib64  -o gadirs gadirs-gadirs.o -lboost_filesystem

All done with standard autotools.

Is there a way to force it to link against the link name?

Isnt that what its there for?

Giles Anderson

reply via email to

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