http://qa.mandrakesoft.com/show_bug.cgi?id=3159
------- Additional Comments From [EMAIL PROTECTED] 2003-03-12 12:26 ------- Honestly I don't understand why problems with ld.so.conf (whether can't prepend or not the default lib paths to /lib /usr/lib is related to this package)? This package provides a backward compatible loader with ld-linux.so.1, for programs still needing a version 1 loader and substantially for libc 5.3.12 based programs. For instance if you want to get old wordperfect 8 running in 9.1, you have to install ld.so1 as well as libc-base-5.3.12 and libc-extras-5.3.12 provided in contrib (libc-base/extras will append /usr/i486-linux-libc5-lib to ld.so.conf). All the programs in the distributions uses the linux loader /lib/ld-linux.so.2 which is not part of this ld.so1 package, but of glibc package. Furthermore for old programs needed a version 1 loader, the loader /lib/ld-linux.so.1.9.1 should still honour the old ld.so.conf behaviour. ------- 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
