Summary: | x11-terms/aterm[background] failes to install /usr/bin/aterm libpng14 issue | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Larson <kaRma0> |
Component: | New packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED CANTFIX | ||
Severity: | major | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robert Larson
2012-01-08 04:55:08 UTC
After doing some digging, I came to find the following: 1. Libpng's site says this: "Apps that compiled against libpng 1.4 without warnings about deprecated features should happily compile against 1.5, too." 2. Extracting the aterm source and grep-ing for 'lpng14' showed no results, so it was being pulled in from somewhere else during configuration. 3. After running ./configure on the source, LIB_AFTERIMAGE gets set in several places and contains "lpng14", so it appears to be an issue with the install of afterstep still using libpng 1.4. 4. Dropping "x11-wm/afterstep ~<arch>" into /etc/portage/package.keywords, upgrading afterstep, and reinstalling aterm fixed this problem. (Hurray!) With that aside, there's still the issue of aterm not failing during the compilation phase. Almost forgot to mention: the version of afterstep that I was using was 2.2.9, and by adding the keywords and upgrading, I'm now at 2.2.11. The issue should be replicable if you set the 'png' USE flag, emerge libpng >=1.5, afterstep =2.2.9, and then aterm. The afterstep rebuild should have been triggered by the revdep-rebuild --library /usr/lib64/libpng14.so.14 which is suggested at the libpng-1.5 emerge. Did you remove /usr/lib64/libpng14.so.14 ? I've some evidence that even if you run this this revdep-rebuild, it doesn't hit. I think the right command should have been "revdep-rebuild --library libpng14.so.14". Anyway, the link problem "-lpng14 missing" only occurs w/ an broken afterstep installation. Please take a look at "revdep-rebuild --ignore -- --ask" from time to time. Yeah, I'm surprised that I overlooked putting that in the comments... I definitely ran revdep-rebuild several times. I can verify - it did not rebuild afterstep. That --ignore option is pretty handy. I've been doing it the old fashioned 'rm -rf' way for a while, it's good to know there's a cleaner way to go about it now! Thanks! |