Summary: | sci-visualization/gnuplot-4.2.6: ld: cannot find -lpng12 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Razvan Cojocaru <razvanco> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | sam |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log
Environment |
Description
Razvan Cojocaru
2010-08-07 09:08:04 UTC
Created attachment 241727 [details]
Build log
Created attachment 241729 [details]
Environment
Also, I do have a libpng12 library: # locate libpng12 /usr/lib/libpng12.so.0 and it looks valid to ldd: # ldd /usr/lib/libpng12.so.0 linux-gate.so.1 => (0xb776e000) libz.so.1 => /lib/libz.so.1 (0xb7715000) libm.so.6 => /lib/libm.so.6 (0xb76ef000) libc.so.6 => /lib/libc.so.6 (0xb75a5000) /lib/ld-linux.so.2 (0xb776f000) nah, you just need to read libpng's postinst message for upgrade instructions... The postinst message says "Run ${EPREFIX}/usr/sbin/libpng-1.4.x-update.sh to fix libtool archives (.la)". As you can see in my initial comment, I've stated that "I did run lafilefixer --justfixit, and libpng-1.4.x-update.sh, and that did not fix the problem". I've also run 'revdep-rebuild -v' after that, and still no go. Other than manually re-emerging all libpng-affected packages I don't see what else I can do. I've done an 'emerge -C libpng', then emerged libpng-1.2, then 'emerge -u libpng' and it's working now. Something fishy is going on, but it looks like it's more of a system-wide quirk (I've switched GCC versions recently, might have something to do with that), so the bug I guess doesn't belong with gnuplot. lafilefixer is useless for the libpng upgrade & plain revdep-rebuild without the --library parameter is also not useful so here goes: 1. /usr/sbin/libpng-1.4.x-update.sh 2. emerge -1 cairo pango gtk+ libglade 3. revdep-rebuild --library libpng12.so.0 if you still have issues after that, please do reopen / open new bug *** Bug 347585 has been marked as a duplicate of this bug. *** |