ldconfig errors with ncurses and other libraries

[maluvia]

While checking a recent build, I ran ldconfig which output the following errors.

Running ldconfig without flags produces these ncurses errors:

ldconfig: can't read header from /usr/local/lib/libpanel.so, skipping
ldconfig: can't read header from /usr/local/lib/libncurses.so, skipping
ldconfig: can't read header from /usr/local/lib/libmenu.so, skipping
ldconfig: can't read header from /usr/local/lib/libform.so, skipping
ldconfig: can't read header from /usr/local/lib/libcursesw.so, skipping
ldconfig: can't read header from /usr/local/lib/libcurses.so, skipping

Running ldconfig -D additionally produces:

ldconfig: uClibc version
/lib:
ldconfig: /lib/librt-2.20.so has inconsistent soname (librt.so.1)
ldconfig: /lib/libnss_dns-2.20.so has inconsistent soname (libnss_dns.so.2)
ldconfig: /lib/libdl-2.20.so has inconsistent soname (libdl.so.2)
ldconfig: /lib/libnss_compat-2.20.so has inconsistent soname (libnss_compat.so.2)
ldconfig: /lib/libc-2.20.so has inconsistent soname (libc.so.6)
ldconfig: /lib/libnss_files-2.20.so has inconsistent soname (libnss_files.so.2)
ldconfig: /lib/ld-2.20.so has inconsistent soname (ld-linux-x86-64.so.2)
ldconfig: /lib/libresolv-2.20.so has inconsistent soname (libresolv.so.2)
ldconfig: /lib/libm-2.20.so has inconsistent soname (libm.so.6)
ldconfig: /lib/libutil-2.20.so has inconsistent soname (libutil.so.1)
ldconfig: /lib/libanl-2.20.so has inconsistent soname (libanl.so.1)
ldconfig: /lib/libnsl-2.20.so has inconsistent soname (libnsl.so.1)
ldconfig: /lib/libpthread-2.20.so has inconsistent soname (libpthread.so.0)
ldconfig: /lib/libcrypt-2.20.so has inconsistent soname (libcrypt.so.1)
ldconfig: /usr/lib/sudo_noexec.so has inconsistent soname (libsudo_noexec.so)
ldconfig: /usr/local/lib/libXaw7.so.7.0.0 has inconsistent soname (libXaw.so.7)
ldconfig: /usr/local/lib/libXaw6.so.6.0.1 has inconsistent soname (libXaw.so.6)

I believe ldconfig is complaining about ncurses because the previous symlinks have been replaced with entries of the form:
 echo "INPUT(-l${lib}w)" > /usr/lib/lib${lib}.so
Which should not be a problem for ldconfig.
I have no idea what the other errors are from

I am wondering if the ldconfig from uclibc is in need of updating, or perhaps needs to be replaced with the one from glibc?

[Juanito]

the ldconfig from glibc is huge compared to the one from uClibc...

[maluvia]

I understand that is why the uclibc version is being used.  I am concerned however, that if ldconfig can't make sense of the ncurses headers, this could lead to problems with other builds which have a hard dependency on ncurses. 

Would it be possible, perhaps, to have the ldconfig from glibc available as it's own optional extension, in the same way that bash is available for those who find the busybox sh insufficient?

[curaga]

Those linker scripts are exclusively for building, and you can ignore those warnings from ldconfig.

You can easily test this:

Code: [Select]

tce-load -wi bash
mkdir /tmp/kai
sudo mv /usr/local/lib/libncurses* /tmp/kai
bash # won't start, can't find ncurses
echo /tmp/kai | sudo tee -a /etc/ld.so.conf
sudo ldconfig
bash # works fine

[maluvia]

I see. That's actually quite a relief :-) Thanks.