Hi. sergey <firstname.lastname@example.org> (27/02/2011): > Is it normal that Debian's programs in my system gets dependencies > from non-Debian libraries? Phrased otherwise, it's normal to get to look into /usr/local/lib since that's the linker's configuration, see /etc/ld.so.conf.d/libc.conf (which has a comment about its being the default libc configuration, so not a Debian-specific issue). > In this situation each new installation in /usr/local is a venture > with unpredictable results. Yes, that's why the local administrator should be very careful when installing stuff there. > Any Debian's program can stop work or can begin work in unexpected > way after installation of new program in /usr/local. It makes Debian > unreliable system. Wrong conclusion. Anyway, here's what you could do: - remove that path from the linker's configuration, and set LD_LIBRARY_PATH when running the set of binaries that need special libraries; - or stop installing into /usr/local, install in other directories, and wrap your binaries to set LD_LIBRARY_PATH=/path/to/that/lib just for those binaries; - or even build your stuff with an RPATH pointing to the right directory if you don't want to wrap your calls. KiBi.
Description: Digital signature