Summary: | revdep-rebuild reports media-gfx/imagemagick-6.5.2.9 broken again and again due to required /usr/lib/libgomp.la | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ivan Yarych <vanya> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | asturm, SebastianLuther |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
revdep-rebuild output
emerge --info |
Description
Ivan Yarych
2009-10-12 19:28:58 UTC
Created attachment 206867 [details]
revdep-rebuild output
Created attachment 206869 [details]
emerge --info
Please try dev-util/lafilefixer. After feeding all the broken .la's to lafixer revdep-rebuild does not complain now. Thank you for the hint! However the question is: won't it break again after next ImageMagick upgrade? (In reply to comment #4) > However the question is: won't it break again after next ImageMagick upgrade? > No, this was caused by removing gmp's la file, which was erroneously referenced by other la files, which is fixed now. It's not gmp's la file, but you get it... (In reply to comment #6) > It's not gmp's la file, but you get it... > (In reply to comment #6) > It's not gmp's la file, but you get it... > i've re-emerged gcc and imagemagick i have run lafilefixer --justfixit and #fix_libtool_files.sh `gcc -dumpversion` --oldarch i586-pc-linux-gnu yet still the problem persists. any idea what to do next (In reply to comment #7) > (In reply to comment #6) > > It's not gmp's la file, but you get it... > > > > (In reply to comment #6) > > It's not gmp's la file, but you get it... > > > > i've re-emerged gcc and imagemagick > i have run lafilefixer --justfixit > and #fix_libtool_files.sh `gcc -dumpversion` --oldarch i586-pc-linux-gnu > yet still the problem persists. any idea what to do next > i do apologise i just change the above cmd i586 to i686. no more problems. *** Bug 307313 has been marked as a duplicate of this bug. *** |