[Cooker] [Bug 3264] [ldconfig] ldconfig doesn't follow stipulated search order for libraries
http://qa.mandrakesoft.com/show_bug.cgi?id=3264 [EMAIL PROTECTED] changed: What|Removed |Added CC||bugzilla- ||[EMAIL PROTECTED] Status|RESOLVED|VERIFIED --- Additional Comments From [EMAIL PROTECTED] 2003-24-06 17:35 --- Multiple submission verified duplicate -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- 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: VERIFIED creation_date: description: I've been running a bug report as bug #3159, and apparently I chose the wrong package so I'll recap that report: This is my understanding of ldconfig: 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. This is the bug: 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. This behaviour appeared somewhere between MDK-7.0 and 8.2 and is till there in 9.1rc2 (well I haven't reported it before and apparently noone else seems to be bugged about it, but I really like to upgrade some libs myself and not use the cooker libs.) Peder
[Cooker] [Bug 3264] [ldconfig] ldconfig doesn't follow stipulated search order for libraries
http://qa.mandrakesoft.com/show_bug.cgi?id=3264 [EMAIL PROTECTED] changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-03-13 19:41 --- don't post the same bug multiple times *** This bug has been marked as a duplicate of 3253 *** --- 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: I've been running a bug report as bug #3159, and apparently I chose the wrong package so I'll recap that report: This is my understanding of ldconfig: 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. This is the bug: 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. This behaviour appeared somewhere between MDK-7.0 and 8.2 and is till there in 9.1rc2 (well I haven't reported it before and apparently noone else seems to be bugged about it, but I really like to upgrade some libs myself and not use the cooker libs.) Peder
