Re: ldconfig issue with raspbian, may affect debian too
Steve McIntyre wrote:
Sorry It seems when I pasted the stuff from irc (while trimming
unrelated stuf) I missed the most important line
That's not the one to look for. You want:
Tag_ABI_VFP_args: VFP registers
which is also set there. "readelf -h" also says
Flags: 0x5000002, has entry point, Version5 EABI
What does "ldconfig -p" say for you on problematic system?
<mike_t> plugwash, http://pastebin.com/6xPrPQbL
root@rpi:~# ldd /opt/vc/bin/vcgencmd
libvcos.so => not found
libvchiq_arm.so => not found
libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0
libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6eda000)
librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb6ecb000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6d9c000)
root@rpi:~# ldconfig -p | fgrep libvcos.so
libvcos.so (libc6) => /opt/vc/lib/libvcos.so
The issue appears to be related to ld.so cache regeneration during
upgrade. It didn't happen for me when I took a slightly older raspberry
pi foundation image and updated it to the latest version but I was able
to reproduce it by doing.
dpkg -i libc-bin_2.13-37+rpi1_armhf.deb
apt-get -f install (which upgrades libc-bin back to 2.13-38)
Once a system is suffering from the issue it is nessacery to remove
/var/cache/ldconfig/aux-cache and run ldconfig. Removing only
/etc/ld.so.cache and running ldconfig is not sufficient.
Based on that it seems the soloution is to make libc.preinst remove
/var/cache/ldconfig/aux-cache as well as /etc/ld.so.cache and bump the
version that triggers the removals. Do others agree?