libcurses.so -> libncurses.so symlink and ldconfig

Tushar Teredesai sukucorp at gmail.com
Thu Aug 4 09:48:03 PDT 2005


On 8/4/05, Alexander E. Patrakov <patrakov at ums.usu.ru> wrote:
> The LFS-6.1 book creates the /usr/lib/libcurses.so -> libncurses.so
> symlink during ncurses installation. A possible problem is that ldconfig
> also looks at that symlink. So after running the following commands as root:
> 
> cd /usr/lib ; /sbin/ldconfig ; ls -l lib{n,}curses*
> 
> the result is something like:
> 
> lrwxrwxrwx  1 root root     12 Jun 23 12:02 libcurses.a -> libncurses.a
> lrwxrwxrwx  1 root root     13 Jun 23 12:03 libcurses.so -> libncurses.so
> -rw-r--r--  1 root root 103046 Jun 23 12:03 libncurses++.a
> -rw-r--r--  1 root root 369990 Jun 23 12:02 libncurses.a
> lrwxrwxrwx  1 root root     25 Jun 23 12:03 libncurses.so ->
> ../../lib/libncurses.so.5
> lrwxrwxrwx  1 root root     12 Jun 23 12:14 libncurses.so.5 -> libcurses.so
> 
> Note the last symlink (created by ldconfig). I don't know if it is a
> real problem (but it sometimes shows e.g. in ldd /bin/bash on
> glibc-2.3.5 based systems).

I don't remember seeing the last link in my previous LFS installations
(maybe it was there and I never noticed it?). But I remember the link
was created in the recent installation. Don't know where the bug lies
(a bug coz I don't think that link is required). I got around it by
using "ldconfig -X" instead of ldconfig when updating the linker
cache.

> If this symlink is indeed bad, it can be
> removed and the libcurses.so -> libncurses.so symlink can be replaced
> with a simple linker script:
> 
> rm libncurses.so.5
> rm libcurses.so
> echo 'INPUT(-lncurses)' >libcurses.so

Sounds good if testing does not reveal any problems.

> 
> If the symlink is a non-problem, sorry for the noise.

-- 
Tushar Teredesai
   mailto:tushar at linuxfromscratch.org
   http://www.linuxfromscratch.org/~tushar/



More information about the lfs-dev mailing list