Description of problem: An attempt to run 'make' for 'demo' directory from GraphicsMagick-perl-1.3.7-1.fc11.x86_64 package results in: $ make perl demo.pl perl: symbol lookup error: /usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/auto/Graphics/Magick/Magick.so: undefined symbol: InitializeMagick make: *** [all] Error 127 With source rpm pulled and after 'rpmbuild --rebuild GraphicsMagick-1.3.7-1.fc11.src.rpm' and reinstallation of GraphicsMagick-perl from a package created that way the problem is gone. It looks like that bug 365901 shows up again. Version-Release number of selected component (if applicable): GraphicsMagick-1.3.7-1.fc11.x86_64 How reproducible: always Additional info: The same issue hits also GraphicsMagick-perl-1.3.7-1.el5.x86_64 now in epel-testing.
This bug affects anything that needs to use the Graphics::Magick perl module. $ perl -MGraphics::Magick -e1 perl: symbol lookup error: /usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/auto/Graphics/Magick/Magick.so: undefined symbol: InitializeMagick
The workaround mentioned in bug 203975 works here: cd /usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/auto/Graphics/Magick mv Magick.so Magick-0.so ld -shared -o Magick.so `pwd`/Magick-0.so /usr/lib64/libGraphicsMagick.so
Problem still exists in Fedora 12.
The current update to GraphicsMagick-perl-1.3.7-4.fc11 suffers from the same affliction.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
As mentioned by Dan Stahlke above, this issue appears to still exit in Fedora 12. Someone needs to bump the version number referenced in this bug so that it stays on radar for Fedora 12.
The issue is the same also for GraphicsMagick-1.3.12-1.fc14, and most likely for fc13 as well (which "Bug Zappers" could easily verify).
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Is there any progress on this? It was originally filed against Fedora 11... the bug has recently been celebrating its first birthday... James
GraphicsMagick-1.3.12-4.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/GraphicsMagick-1.3.12-4.fc15
Package GraphicsMagick-1.3.12-4.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing GraphicsMagick-1.3.12-4.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/GraphicsMagick-1.3.12-4.fc15 then log in and leave karma (feedback).
GraphicsMagick-1.3.12-4.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.