Bug 172754

I tried recompiling ImageMagick on my system, but this didn't fix it.

Tried to rebuild ImageMagick against current rawhide (to see if might fix the
problem) and I get this error (which I think is related):

extracting debug info from /var/tmp/ImageMagick-6.2.5.4-root/usr/bin/composite
extracting debug info from /var/tmp/ImageMagick-6.2.5.4-root/usr/bin/conjure
extracting debug info from /var/tmp/ImageMagick-6.2.5.4-root/usr/bin/montage
extracting debug info from /var/tmp/ImageMagick-6.2.5.4-root/usr/bin/animate
extracting debug info from /var/tmp/ImageMagick-6.2.5.4-root/usr/bin/compare
extracting debug info from /var/tmp/ImageMagick-6.2.5.4-root/usr/bin/identify
extracting debug info from /var/tmp/ImageMagick-6.2.5.4-root/usr/bin/mogrify
extracting debug info from /var/tmp/ImageMagick-6.2.5.4-root/usr/bin/import
extracting debug info from /var/tmp/ImageMagick-6.2.5.4-root/usr/bin/convert
extracting debug info from /var/tmp/ImageMagick-6.2.5.4-root/usr/bin/display
cpio: ImageMagick-6.2.5/<built-in>: No such file or directory
cpio: ImageMagick-6.2.5/PerlMagick/Magick.c: No such file or directory
20934 blocks
+ /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot
*******************************************************************************
*
* WARNING: 'check-rpaths' detected a broken RPATH and will cause 'rpmbuild'
*          to fail. To ignore these errors, you can set the '$QA_RPATHS'
*          environment variable which is a bitmask allowing the values
*          below. The current value of QA_RPATHS is 0x0000.
*
*    0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
*               issue but are introducing redundant searchpaths without
*               providing a benefit. They can also cause errors in multilib
*               environments.
*    0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
*               nor relative filenames and can therefore be a SECURITY risk
*    0x0004 ... insecure RPATHs; these are relative RPATHs which are a
*               SECURITY risk
*    0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
*               RPATHs; this is just a minor issue but usually unwanted
*    0x0010 ... the RPATH is empty; there is no reason for such RPATHs
*               and they cause unneeded work while loading libraries
*    0x0020 ... an RPATH references '..' of an absolute path; this will break
*               the functionality when the path before '..' is a symlink
*
*
* Examples:
* - to ignore standard and empty RPATHs, execute 'rpmbuild' like
*   $ QA_RPATHS=$[ 0x0001|0x0010 ] rpmbuild my-package.src.rpm
* - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
*   $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
*
* 'check-rpaths' is part of 'fedora-rpmdevtools'.
*
*******************************************************************************
ERROR   0001: file '/usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi/aut
o/Image/Magick/Magick.so' contains a standard rpath '/usr/lib' in [/usr/lib:/usr
/X11R6/lib]
ERROR   0001: file '/usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi/aut
o/Image/Magick/Magick.so' contains a standard rpath '/usr/X11R6/lib' in [/usr/li
b:/usr/X11R6/lib]
error: Bad exit status from /var/tmp/rpm-tmp.33053 (%install)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.33053 (%install)
[rodd@localhost ~]$

I need to get ImageMagick working again.

Can anyone advise how I might do this.  Is this problem related to ImageMagick,
or is perl missing something?

I haven't got any older RPMs that I can use (and FC4 RPMs won't install) but I'm
happy to build stuff if that's what it takes.  I'm assuming I can pull something
from CVS, but I don't know what or how.

Here's hoping someone can help.

The gcc 4.1 mass rebuild seems to have succeeded in rebuilding this...