Libtool problem with shared lib in non-standard directory

2006-01-26 Thread Marcel Loose
Hi, I orginally posted this http://lists.gnu.org/archive/html/bug-libtool/2006-01/msg1.html mail to the [EMAIL PROTECTED] It seems to be a bug in libtool. Hence, I will try to provide some extra information. I have a package "Common" that (optionally) uses the 3rd party package Boost.T

Re: Libtool problem with shared lib in non-standard directory

2006-01-08 Thread Ralf Wildenhues
Hi Marcel, * Marcel Loose wrote on Thu, Jan 05, 2006 at 12:31:35PM CET: > > I encountered a problem where libtool does not add a -rpath to all the > libs it adds on the link line. I'll try to describe the problem. > > I have two packages that are developed in-house, let's call them A and > B. Pa

Re: Libtool problem with shared lib in non-standard directory

2006-01-26 Thread Ralf Wildenhues
Hi Marcel, * Marcel Loose wrote on Thu, Jan 26, 2006 at 11:07:02AM CET: > > I have a package "Common" that (optionally) uses the 3rd party package > Boost.Threads (and log4cplus). Another package "Blob" depends on > "Common". Whenever I try to run the test (using make check) on the > "Blob" test

Re: Libtool problem with shared lib in non-standard directory

2006-01-26 Thread Ralf Wildenhues
> * Marcel Loose wrote on Thu, Jan 26, 2006 at 11:07:02AM CET: > > > > I have a package "Common" that (optionally) uses the 3rd party package > > Boost.Threads (and log4cplus). Another package "Blob" depends on > > "Common". Whenever I try to run the test (using make check) on the > > "Blob" test

Re: Libtool problem with shared lib in non-standard directory

2006-01-27 Thread Marcel Loose
Hi Ralf, The extra info is below. Hope it helps. Regards, Marcel Loose. >>> Ralf Wildenhues <[EMAIL PROTECTED]> 26-01-06 13:56 >>> *snip* > Could you also show the link line for creating libblob.la plus libtool > output, and if it is relinked upon installation, also the same from the