Jan Ulrich Hasecke <[EMAIL PROTECTED]> writes: > I <[EMAIL PROTECTED]> wrote: > > > Brian Nelson <[EMAIL PROTECTED]> writes: > > > > > > /usr/bin/WindowMaker: relocation error: /usr/bin/WindowMaker: undefined > > > > symbol: RReleaseImage > > > > > [...] > > > > > ldd /usr/bin/WindowMaker > > libwraster.so.2 => /usr/local/lib/libwraster.so.2 (0x40023000) > > libtiff.so.3 => /usr/lib/libtiff.so.3 (0x40037000) > > libXpm.so.4 => /usr/X11R6/lib/libXpm.so.4 (0x40079000) > > libHermes.so.1 => /usr/lib/libHermes.so.1 (0x40088000) > > [...] > > > > > Mh, Why is WindowMaker linked against libwraster.so.2 in > > /usr/local/lib ? > > I solved it this way. I moved libwraster.so.2 in /usr/local to > .libwraster.so.2 and reinstalled wmaker. > > Now it is linked against /usr/lib/libwraster.so.2 > > Is this the normal debian-way? First linking against libs in > /usr/local/lib and if not found linking against /usr/lib ?
I'm not sure. In Debian, /usr/local/bin by default does have priority over /usr/bin, but I thought ld only "trusts" /lib and /usr/lib. At least that's what the manpage says... > Can I force dpkg via apt-get to link against /usr/lib when I have some > libs in /usr/local/lib ? No, it's a run-time problem rather than packaging problem. Before execution, you'd want to either edit /etc/ld.so.conf and run ldconfig, or less ideally set the LD_LIBRARY_PATH environment variable. However, I think the best solution would be to not change any linker settings, but rather clean out the cruft out of your /usr/local directory. -- Brian Nelson <[EMAIL PROTECTED]>
