LD_LIBRARY_PATH not being honoured (Re: Crash on launch with no X error message)

[Martijn Klingens]

On Monday 23 February 2004 14:43, Richard Smith wrote:
> Duncan and I have both experienced this now, and it's stopping me from
> running BRANCH. It looks like kopete's being linked against the wrong
> libkopete, and it's being done by absolute path. Setting LD_LIBRARY_PATH
> does not override it.
> 
> I have KDE installed from CVS in DIR1=/home/tla/kde-cvs and kopete 0.8
> installed in DIR2=/home/tla/packages/kopete-0.8rc1.
> 
> ldd DIR2/bin/kopete tells me it's linked to DIR1/lib/libkopete.so.1, and no
> amount of playing with LD_LIBRARY_PATH changes that. However, moving DIR1
> /lib/libkopete.so.1 makes it see DIR2/lib/libkopete.so.1, and then Kopete
> 0.8 runs.
> 
> I can only assume we have either the wrong magic in kopete/Makefile.am or in
> libkopete/Makefile.am, but I don't know enough automake to diagnose or fix
> this.

Sounds like a problem with the KDE build system, because it should never 
hardcode paths in the .so files. I also fail to see how Makefile.am can be of 
any influence, but's about as far as my knowledge goes.

Cross-posting to core-devel, hopefully someone there knows what's going on.

-- 
Martijn