[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Strange goings on with Juk (FC3, KDE Branch 3.5)
From:       "Steven P. Ulrick" <lists () afolkey2 ! net>
Date:       2005-09-30 3:17:49
Message-ID: 20050929221749.720ed2c3 () afolkey2 ! net
[Download RAW message or body]

On Thu, 29 Sep 2005 23:10:08 -0400
Michael Pyne <pynm0001@unf.edu> wrote:

> On Thursday 29 September 2005 22:53, Steven P. Ulrick wrote:
> > > Can you run ldd on the juk 2.3 binary and see what libraries it is
> > > trying to link against while you are in your normal KDE
> > > environment?
> >
> > Hello, Michael
> > Here it is:
> > http://www.afolkey2.net/juk-ldd.txt
> >
> > Thanks again,
> > Steven P. Ulrick
> 
> Yeah, that's your problem:
> 
> <snip>
> 	libkparts.so.2 => /usr//lib/libkparts.so.2 (0x0016e000)
> 	libkutils.so.1 => /usr//lib/libkutils.so.1 (0x00c0c000)
> 	libartskde.so.1 => /usr//lib/libartskde.so.1 (0x001d5000)
> 	libkio.so.4 => /usr//lib/libkio.so.4 (0x026ff000)
> 	libkdeui.so.4 => /usr//lib/libkdeui.so.4 (0x07c51000)
> 	libkdesu.so.4 => /usr//lib/libkdesu.so.4 (0x0051d000)
> </snip>
> 
> You'll notice that most of your KDE libraries are being found
> in /usr/lib instead of /usr/local/kde-svn/lib like akode:
> 
> 	libakode.so.2 => /usr/local/kde-svn/lib/libakode.so.2
> (0x00f2b000)
> 
> Now, the double-slash thing (/usr//lib) is odd.  I'm not sure what
> would cause that other than libtool being stupid.  Do you explicity
> set --prefix when configuring your modules?

Yes, I explicitly set --prefix for each module thusly: "--prefix=/usr/local/kde-svn"

Have a Great Night,
Steven P. Ulrick

> If you don't then the
> configure script might pick up the wrong library directory when
> trying to link the executables.  Although judging from the ldd output
> it looks like the executable correctly looks for only the soname
> (e.g. libkdesu.so.4 instead of the full path), it apparently has a
> hardcoded /usr//lib embedded in the executable.  I'm not sure what
> part of libtool causes that or would fix it though. :(
> 
> As far as why the Fedora juk finds the correct libraries, perhaps
> their executables don't have dynamic path entries embedded, and so
> the dynamic linker uses LD_LIBRARY_PATH instead of the
> missing /usr//lib information?
> 
> Regards,
>  - Michael Pyne
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]