I was doing revdep-rebuild --library libjpeg.so.62 which figured out that imagemagick must be rebuilt. Then I did a crontrol check - ran regular revdep-rebuild - two packages showed up, including imagemagick. Then another round checking - and I see imagemagick again. Reproducible: Always Steps to Reproduce: 1. revdep-rebuild - imagemagick broken 2. revdep-rebuild again - imagemagick is broken again 3. Actual Results: imagemagick is broken on every revdep-rebuild run Expected Results: imagemagick should be rebuilt without the need for second rebuilding. There are a lot of broken .la files in /usr/lib/ImageMagick-6.5.2/modules-Q16/coders/ that require /usr/lib/libgomp.la
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. ***