http://qa.mandrakesoft.com/show_bug.cgi?id=3159
------- Additional Comments From [EMAIL PROTECTED] 2003-03-12 12:01 ------- I'm sorry if I'm being annoying or not getting the point but AFAIK: During run-time the program should check LD_LIBRARY_PATH, /etc/ld.so.cache and default libs. 'ldconfig' is used to update the cache using LD_LIBRARY_PATH, /etc/ld.so.conf and default libs as the search order. 'ldconfig -p' shows what's in the cache and in what order the libraries are referenced, so if /usr/lib/libmylib.so comes before /usr/local/lib/libmylib.so the former is used at runtime. When I run 'ldconfig -p | grep libfreetype' I get (in order) libfreetype.so (libc6) => /usr/lib/libfreetype.so.6 libfreetype.so (libc6) => /usr/local/lib/libfreetype.so.6 and 'ldd /opt/xfce4_cvs26feb/bin/xfwm4 | grep freetype' gives libfreetype.so.6 => /usr/lib/libfreetype.so.6 So even though my ld.so.conf has /usr/local/lib first ldconfig and the linker ignores it and chooses the default lib instead. I think that's a bug and if you think it's glibc's fault please tell me and I'll start bugging (pun intended) those guys. Oh, and I think the compiler (or autoconf or whatever) should adhere to the same standards, but perhaps that's another issue. Peder ------- 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
