Description of problem:
rpmbuild(8) gets confused by ENV(PERL_MM_OPT).
Version-Release number of selected component (if applicable):
PERL_MM_OPT="PREFIX=/root" rpmbuild --rebuild
+ find /var/tmp/ImageMagick-18.104.22.168-root/usr/lib/perl5/site_perl/5.8.3
-type d -name Image
No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.7795 (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.7795 (%install)
successfully built package
Created attachment 103995 [details]
Patch to delete ENV(PERL_MM_OPT) for %build and %install
PERL_MM_OPT needs to be dealt with in ImageMagick.spec, not
in default rpmbuild configuration.
One could also fix in build system setup by controlling for
what is in the environment when rpmbuild is invoked.
> PERL_MM_OPT needs to be dealt with in ImageMagick.spec
PERL_MM_OPT could be handled by all the packages building any Perl
modules. As the handling would be always the same. Therefore I think
it is more systematic approach to normalize Perl build environment by
Otherwise there is a need to post 100+ bugreports or so.
ENV(PERL_MM_OPT) is the same category as ENV(CLASSPATH) or umask(1)
already handled by %___build_pre.
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
The bug is still valid for: rpm-4.4.1-18.1
To prove it is not ImageMagick related you can try this command:
PERL_MM_OPT='PREFIX=/home/lace' rpmbuild --rebuild
Attached patch fixes it.
Added in rpm-4.4.3-0.26 when built.