On Fri, Feb 23, 2007 at 11:16:41AM -0700, Jonathan Corbet wrote:
Foiled again. Time to investigate...
% cd /usr/lib64
% ls -l *curses*
-rw-r--r-- 1 root root 17 2007-02-19 06:17 libcurses.so
lrwxrwxrwx 1 root root 14 2007-02-20 09:30 libcursesw.so -> libncursesw.so
lrwxrwxrwx 1 root root 27 2007-02-20 09:30 libncurses.so ->
../../lib64/libncurses.so.5
lrwxrwxrwx 1 root root 12 2006-12-02 10:23 libncurses.so.5 -> libcurses.so
lrwxrwxrwx 1 root root 16 2007-02-20 09:30 libncursesw.so -> libncursesw.so.5
lrwxrwxrwx 1 root root 18 2007-02-20 09:29 libncursesw.so.5 ->
libncursesw.so.5.6
-rwxr-xr-x 1 root root 278536 2007-02-19 06:17 libncursesw.so.5.6
libncurses.so.5 points to libcurses.so (without an "n") which is,
indeed, a short file:
% cat libcurses.so
INPUT(-lncurses)
That's rather short of the entry points I would ordinarily expect to
find in a curses library. Plus it's an ascii file.
My ncurses packages verify fine, so I don't *think* this is a
locally-hosed system.
Just rm -f /usr/lib*/libncurses.so.5, perhaps rerun /sbin/ldconfig
and things ought to be fine. Wonder if ncurses package should delete
this symlink in %post or something similar (though I believe it is just
older rawhide ncurses that would need such a fixup).
/usr/lib*/libcurses.so is now a linker script rather than symlink, because
as the real libncurses.so.5.6 library is in /lib*/ now instead of /usr/lib*/
and libcurses.so was a symlink to libncurses.so, ldconfig kept recreating
the bogus /usr/lib*/libncurses.so.5 symlink. For details see
#228891.
Jakub