Summary: | media-gfx/optipng-0.7.4 built with libpng-1.2.44 but running with 1.6.7, Out of memory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Massimo Burcheri <burcheri.massimo+bugs-gentoo> |
Component: | Current packages | Assignee: | Sebastian Pipping <sping> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | sping |
Priority: | Normal | Keywords: | PATCH |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.gentoo.org/show_bug.cgi?id=494616#c4 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
media-gfx:optipng-0.7.3:20131218-122235.log
emerge --info media-libs/libpng media-gfx/optipng ls -l /usr/include/*png* /usr/lib/*png* |
Description
Massimo Burcheri
2013-12-18 07:45:15 UTC
I also tried re-emerge with -static-libs: USE="-static-libs" emerge -atv libpng optipng the message implies optipng was compiled using headers from libpng 1.2, but the libpng 1.2 from SLOT="1.2" you might have co-installed with 1.6 doesn't install any headers at all so, got old libpng headers at /usr/local/include (or perhaps even /usr/include) ? you definately shouldn't, only libpng 1.6 headers should be there: ssuominen@null ~ $ ls -ld /usr/include/libpng* drwxr-xr-x 2 root root 4096 Dec 1 09:50 /usr/include/libpng16 ssuominen@null ~ $ ls -ld /usr/local/include/libpng* ls: cannot access /usr/local/include/libpng*: No such file or directory Current installation of libpng is amd64 stable only now: $ ls -ld /usr/include/libpng* drwxrwxr-x 2 root root 4,0K Dez 18 10:43 /usr/include/libpng15/ $ ls -ld /usr/local/include/libpng* ls: cannot access /usr/local/include/libpng*: No such file or directory $ emerge --info media-libs/libpng ... ================================================================= Package Settings ================================================================= media-libs/libpng-1.2.50 was built with the following: USE="(multilib)" ABI_X86="64" media-libs/libpng-1.5.17-r1 was built with the following: USE="apng static-libs (-neon)" $ ls -al /usr/lib64/libpng*.so* -rwxr-xr-x 1 root root 155K Dez 17 12:15 /usr/lib64/libpng12.so.0* lrwxrwxrwx 1 root root 19 Dez 18 10:43 /usr/lib64/libpng15.so -> libpng15.so.15.17.0* lrwxrwxrwx 1 root root 19 Dez 18 10:43 /usr/lib64/libpng15.so.15 -> libpng15.so.15.17.0* -rwxr-xr-x 1 root root 186K Apr 24 2013 /usr/lib64/libpng15.so.15.15.0* -rwxr-xr-x 1 root root 183K Dez 18 10:43 /usr/lib64/libpng15.so.15.17.0* lrwxrwxrwx 1 root root 11 Dez 18 10:43 /usr/lib64/libpng.so -> libpng15.so* There is some libpng12 left, but this did not help either: $ mv /usr/lib64/libpng12.so.0 /usr/lib64/libpng12.so.0.old && emerge optipng $ mv /usr/lib64/libpng12.so.0.old /usr/lib64/libpng12.so.0 The .ebuild should remove the package shipped old libpng headers, like so: optipng-0.7.4.ebuild: rm -R src/{libpng,zlib} || die And the libpng.pc point to the latest headers: $ pkg-config --cflags libpng -I/usr/include/libpng16 Really, this isn't hard to figure out. It's a simple mismatch of headers and the library. But if you really can't provide the details why it happened, then at least provide comprehensive outputs like the complete optipng build.log, emerge --info, ls -l /usr/include/*png*, ls -l /usr/lib/*png*, and such listings Thanks. Created attachment 365596 [details]
media-gfx:optipng-0.7.3:20131218-122235.log
Created attachment 365598 [details]
emerge --info media-libs/libpng media-gfx/optipng
Created attachment 365600 [details]
ls -l /usr/include/*png* /usr/lib/*png*
No updates and not fixed yet. If this isn't hard to figure out, so at least how can this be fixed, no matter what was leading to this situation? Still valid with 0.7.6? Hi! Neither optipng-0.7.4 nor libpng-1.2.44 are in Gentoo, still. I would dare to close this one as obsolete. Massimo, if you run into it again, please re-open and we try to get it fixed in time, next time. Okay? Best, Sebastian PS: There is mentioned rm -R src/{libpng,zlib} || die in the (one and only 0.7.6) ebuild by now. 0.7.6 is working fine today. (In reply to Massimo Burcheri from comment #12) > 0.7.6 is working fine today. Thanks for the update! |