Messages in this thread | | | Date | Sun, 30 Mar 1997 20:42:41 -0500 (EST) | From | <> | Subject | ld.so 1.9.1 and glibc 2.0.1 |
| |
while running ld.so.1.8.5, compilation and link of glibc 2.0.1 into /usr/local/lib which is the first library in /etc/ld.so.conf resulted in 'unable to load library-inconsistent soname' when ldconfig was executed.
after upgrade to ld.so.1.9.1 the glibc 2.0.1 libraries appear to load (at least ldconfig is not complaining) however attempts to use these same libraries from a user program result in 'load failed for <arg>' where arg is the name of a symbolic link to a glibc 2.0.1 library. these links do exist and are valid but do not cross directory boundries.
strace of an affected program suggests the library lookup is being performed against /usr/lib ie stat("/usr/lib/libc.so.6"). in my case there is no such file.
i should further mention that 'ldconfig -p' of ld.so.1.9.1 characterizes all glibc 2.0.1 libraries as 'ELF libc6'.
i dimly recall a changelog notice for ld.so suggesting it was being modified to not follow a link for certain cases.
could this be an example? if not can ld..so be functioning correctly?
bill
| |