libncurses.so symlink is pointing to wrong location

Bug #75883 reported by Roman Plessl
2
Affects Status Importance Assigned to Milestone
ncurses (Ubuntu)
Fix Released
Undecided
Matthias Klose

Bug Description

Binary package hint: lib32ncurses5-dev

On a amd64 system running Ubuntu 6.10 the symlink of
/usr/lib32/libncurses.so is pointing to the wrong directory/
wrong architecture:

myserver:/# ls -l /usr/lib32/libncurses.so
lrwxrwxrwx 1 root root 25 Dec 12 16:35 /usr/lib32/libncurses.so -> ../../lib/libncurses.so.5

myserver:/# file /lib/libncurses.so.5
/lib/libncurses.so.5: symbolic link to `libncurses.so.5.5'

myserver:/# file /lib/libncurses.so.5.5
/lib/libncurses.so.5.5: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), stripped

I suppose the symlink at /usr/lib32/libncurses.so should point
to /lib32/libncurses.so.

myserver:/# file /lib32/libncurses.so.5.5
/lib32/libncurses.so.5.5: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped

In difference to the other libraries in /usr/lib32/ the libncurses.so
symlink is the only one using relative pathes (../../lib and so one);
maybe that should be changed to the "other" scheme.

Revision history for this message
Matthias Klose (doko) wrote :

fixed in 5.5-5ubuntu3

Changed in ncurses:
status: Unconfirmed → Fix Released
assignee: nobody → doko
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.