On Wednesday 21 December 2005 02:18, Thiago Macieira wrote:
> Craig Howard wrote:
> >Shouldn't having LD_LIBRARY_PATH set cause libraries to be searched from
> > those paths before /usr/lib?
>
> Only if your program was compiled with no --rpath or if it was compiled
> with --enable-new-dtags (ld arguments).
>
> Otherwise, LD_LIBRARY_PATH is not searched.

Hmmm, rpath.

From my i686 laptop system:
; uname -a
Linux laptop 2.6.14-20051111 #1 PREEMPT Fri Nov 11 01:22:55 EST 2005 i686 
GNU/Linux
; objdump -p libkio.so | grep RPATH
  
RPATH       /home/craig/local/kde/root/lib:/home/craig/local/kde/src/qt-copy/lib:/usr/X11R6/lib

Now from my x86_64 system:
; uname -a
Linux jester 2.6.14-22051217 #2 Sat Dec 17 13:01:26 PST 2005 x86_64 GNU/Linux
; objdump -p libkio.so | grep RPATH
  
RPATH       /home/craig/local/kde/root/lib:/usr/lib:/home/craig/local/kde/src/qt-copy/lib:/lib:/usr/X11R6/lib

Note that the second entry in the RPATH is /usr/lib and it comes before my qt 
directory!  I'm sure that's what caused my problems.

Both libraries were built using the same ~/.kdesvn-build file (except for the 
change in march).  There's nothing funky in there, just --enable-debug and 
the default kdesvnbuild linker flags (-Wl,-O1).  I tried unsetting the linker 
options, but that didn't matter.

Where are those extra RPATH entries coming from?  

Is there a way to make unsermake print out the gcc/ld commands it's running?
-- 

Craig Howard
craig@choward.ca
Bachelor of Math - Computer Science 2005
University of Waterloo
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<