There's only libpng12.so.0 created in /usr/lib, when gtk+ and some others requiring libpng12.{,l}a. Non-slotted ebuild doesn't have such a behaviour. Reproducible: Always
and there shouldn't. the slotted version is for binary-only applications, only the .so is required. it's designed to be co-installed with >= libpng-1.4.
(In reply to comment #1) > and there shouldn't. > > the slotted version is for binary-only applications, only the .so is required. > it's designed to be co-installed with >= libpng-1.4. > So how am i supposed install gtk+ then?
(In reply to comment #2) > (In reply to comment #1) > > and there shouldn't. > > > > the slotted version is for binary-only applications, only the .so is required. > > it's designed to be co-installed with >= libpng-1.4. > > > > So how am i supposed install gtk+ then? > If you just upgraded to libpng-1.4.2, then you need to run the script that came with it, `/usr/sbin/libpng-1.4.x-update.sh` to fix .la files, likely also re-emerge x11-libs/cairo, and run `revdep-rebuild --library libpng12.so.0`. (Hard to say because you never posted a build.log of gtk+ failing. :-)
(In reply to comment #3) > > If you just upgraded to libpng-1.4.2, then you need to run the script that came > with it, `/usr/sbin/libpng-1.4.x-update.sh` to fix .la files, likely also > re-emerge x11-libs/cairo, and run `revdep-rebuild --library libpng12.so.0`. > > (Hard to say because you never posted a build.log of gtk+ failing. :-) > Thanks, this fixed the problem. I really should've read these elog's :3 Sorry for the noise.