In regard to: libtool 1.4.3 searches /usr/lib before -L, Pieter...:
>I've asked for help about this problem twice in the last
>few weeks, without any replies.
I saw your posts, but don't recall whether this is something you've
tried with libtool 1.5.2 or not. Have you? T
I've asked for help about this problem twice in the last
few weeks, without any replies.
In the meantime I've done some searching in the libtool
list history, and I came across this:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg04324.html
This seems to be exactly the same problem I'm having.
Dixit Albert Chin (2003-10-21 10:47):
> > The -L option correctly points to the src/verbiste directory, where the
> > newer library has been compiled. However, libtool generates this g++
> > command to do the linking:
> >
> > g++ -g -Wall -o french-conjugator
> > french_conjugator-fre
On Mon, Oct 20, 2003 at 07:32:21PM -0400, Pierre Sarrazin wrote:
> I have a C++ package that contains a library and two command-line
> tools. If I install this package through an RPM (on a RedHat 8.0
> system), I endup with the lib*.la and lib*.so files in /usr/lib.
> I get into trouble when I com
I'm having a problem related to the path that libtool (1.4.3)
uses to search for libraries.
I have a C++ package that contains a library and two command-line
tools. If I install this package through an RPM (on a RedHat 8.0
system), I endup with the lib*.la and lib*.so files in /usr/lib.
I get int
