LinuxQuestions.org - Raspberry Pi ldconfig conflict

- Slackware - ARM (https://www.linuxquestions.org/questions/slackware-arm-108/)

- - Raspberry Pi ldconfig conflict (https://www.linuxquestions.org/questions/slackware-arm-108/raspberry-pi-ldconfig-conflict-4175508295/)

Raspberry Pi ldconfig conflict

I did a fresh install of SlackwareARM current on RaspberryPi model B and when i upgrade to current using slackpkg i can see these alarms on every package when it is installing:

Code:

Verifying package grep-2.18-arm-1.txz.

Installing package grep-2.18-arm-1.txz:

PACKAGE DESCRIPTION:

# grep (print lines matching a pattern)

#

# This is GNU grep, the "fastest grep in the west" (we hope).  Grep

# searches through textual input for lines which contain a match to a

# specified pattern and then prints the matching lines.

#

/sbin/ldconfig: libraries libnsl-2.17.so and libnsl-2.19.so in directory /lib have same soname but different type.

/sbin/ldconfig: libraries libnss_db-2.17.so and libnss_db-2.19.so in directory /lib have same soname but different type.

/sbin/ldconfig: libraries libcrypt-2.17.so and libcrypt-2.19.so in directory /lib have same soname but different type.

/sbin/ldconfig: libraries libnss_nis-2.17.so and libnss_nis-2.19.so in directory /lib have same soname but different type.

/sbin/ldconfig: libraries libnss_compat-2.17.so and libnss_compat-2.19.so in directory /lib have same soname but different type.

/sbin/ldconfig: libraries libcidn-2.17.so and libcidn-2.19.so in directory /lib have same soname but different type.

/sbin/ldconfig: libraries libBrokenLocale-2.17.so and libBrokenLocale-2.19.so in directory /lib have same soname but different type.

This means that i have two libraries to every line above?

Yes, it means what you said.

Remove the 2.17's in /lib and see what happens.

You should be able to see the whole story w/ something like:

Code:

ls -l /lib/*libnsl*

Result of ls -l /lib/*libnsl* :

Code:

root@rpi:~# ls -l /lib/*libnsl*

-rwxr-xr-x 1 root root 99418 Out 28  2013 /lib/libnsl-2.17.so*

-rwxr-xr-x 1 root root 99418 Mai 18 15:51 /lib/libnsl-2.19.so*

lrwxrwxrwx 1 root root    14 Jun 17 18:11 /lib/libnsl.so.1 -> libnsl-2.19.so*

It seems a problem when i installed or upgraded the 2.17 version of that libraries.
Its safe if i rm /lib/libnsl-2.17.so or i should try figure out what else it is point to version 2.17 ?

I would remove them if it was my own system, though I don't want to recommend it to you because I don't know if it may have any consequences :).

Maybe you can move them into a directory somewhere not in /lib and if something breaks copy them back. I think it'll be fine to remove, though.

Quote:

Originally Posted by frushiyama (Post 5189501)

/sbin/ldconfig: libraries libcidn-2.17.so and libcidn-2.19.so in directory /lib have same soname but different type.
/sbin/ldconfig: libraries libBrokenLocale-2.17.so and libBrokenLocale-2.19.so in directory /lib have same soname but different type.[/code]
This means that i have two libraries to every line above?

You most likely have the old 2.17 libraries because you did not yet upgrade the glibc-solibs package.

The warning about 'different type' is due to a bug in glibc 2.17 (or maybe 2.18, I forget which) which has been patched in 2.19.

You should upgrade the glibc-solibs package which should remove those duplicate library names.

Your paste also shows you're installing glibc-2.18 but have 2.19 already installed.

I had the recent updates, checked with:

Code:

root@rpi:/lib# ls -a /var/log/packages/ | grep glibc

glibc-2.19-arm-1

glibc-i18n-2.19-arm-1

glibc-profile-2.19-arm-1

glibc-solibs-2.19-arm-1

glibc-zoneinfo-2014b-noarch-1

And try to reinstall all glibc packages, but even with this the results was the same.
So i did a backup of the 2.17 version of libraries and then it seems solved.
I will let it running and will install some stuff to see if more problem will occur.

Quote:

Originally Posted by frushiyama (Post 5190302)

I had the recent updates, checked with:

Code:

root@rpi:/lib# ls -a /var/log/packages/ | grep glibc

glibc-2.19-arm-1

glibc-i18n-2.19-arm-1

glibc-profile-2.19-arm-1

glibc-solibs-2.19-arm-1

glibc-zoneinfo-2014b-noarch-1

The warnings from ldconfig are just noise and can be ignored.
The fix is to run, which will re-create the auxiliary cache:

Code:

ldconfig -i

It's expected that there are orphaned files from glibc since the pkgtools have no knowledge that the libraries have switched location (they're packaged in /lib/incoming). You would most likely have seen warnings from ldconfig about other libraries and this is due to them appearing in the aaa_elflibs package.

I'll include the fix in the UPGRADE docs for the next release; or patch glibc if there's a patch package for 14.1 prior to the next Slackware release.