On Sun, 25 Jan 2015 00:18:32 -0500 Philip Webb wrote: > After exactly 2 years , I'm trying to update my Asus EEE netbook. > I've emerged gcc-4.8.3 ( 3 h 31 m ), portage-2.2.14 & udev-216 . > However, I've lost X : trying to update gtk+ , I've run into a problem : > it requires Mesa & Cairo & both require libdrm-2.4.58 , > which refuses to compile, failing with lines reporting > that "libpng15.so.15 & libudev.so.0 not found", > which seem to be needed by Cairo & Mesa, which depend on Libdrm ; > I've already updated to libpng-1.6.16 , so libpng16.so.16 is installed. > I've tried 'emerge --nodeps' with Cairo & Mesa, but both fail. > > libdrm-2.4.58 was emerged on this desktop machine without any difficulty > with libpng-1.6.16 emerged a bit later & everything working properly. > > I've done searches of Bugs, Forum & asked Google without much help. > > Can anyone suggest what might be causing this problem ? As for libpng: the problem is that after libpng update many pkg-config files still contain references to old libpng15.so. Usual way to fix this is to rebuild all libpng dependencies (emerge @revdep-rebuild or revdep-rebuild tool may be used for that). But this doesn't work on too old setups, where during such updates packages will require some newer stuff like libdrm to be updated itself.
In order to broke this look you can manually edit all files in /usr/lib/pkgconfig in order to point them to proper libpng version, e.g.: $ cd /usr/lib/pkgconfig $ sed -i 's/libpng15/libpng16/ *.pc As for libudev, probably problem and solution is the same. Not all packages use pkg-config, some have $packagename-config scripts (like fltk-config). Some of these scripts hardcode library names in a similar way to pkg-config, so you have to fix this /usr/bin-*config scripts too if you have any problems with related applications. Best regards, Andrew Savchenko
pgpcS7xPynewa.pgp
Description: PGP signature
