http://qa.mandrakesoft.com/show_bug.cgi?id=3159
------- Additional Comments From [EMAIL PROTECTED] 2003-03-12 08:55 ------- Gwenole. Maybe I expressed myself a bit unclear. I always add /usr/local/lib to /etc/ld.so.conf first thing after installing a distro putting it first in the file. When I had the same library in /usr/lib and /usr/local/lib in MDK-7.0 and ran 'ldconfig -p | grep <libname>' I got my /usr/local/lib/<libname> first and /usr/lib/<libname> second, and this made ./configure use my lib instead of the system default one. This is changed when I ldconfig MDK-8.0, often resulting in errors since the compilation tries to use the headers from /usr/local/include with the lib from /usr/lib. G�tz. No I can't mess everything up; I know what I'm doing :) And I use the excellent 'stow' command which allows me to keep everything in /opt/<progname> and only link the subdirs to /usr/local (only in Debian by default, why??). Sometimes there isn't even an rpm of the version I need. Once a distribution gets out the latest versions of things isn't always available, well perhaps in cooker, but I'd rather keep the default rpm and manage my own libs. And programs should honour user defined paths before built-ins. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: RESOLVED creation_date: description: Somewhere between MDK 7.0 and 8.2 ldconfig changed behaviour to list /lib and /usr/lib before the self specified paths in /etc/ld.so.conf. This has the negative impact that if I compile a new alsa for instance, every other program I subsequently compile tries to link against the preinstalled libs in /usr/lib instead of my new ones in /usr/local/lib
