Description of problem: subversion SRPM rebuild fails with the following errors on powerpc: # ppc rpmbuild --target=ppc --rebuild subversion-1.1.1-2.1.src.rpm <snip> /var/tmp/subversion-root/usr/lib/python2.3/site-packages/libsvn/_ra.la /var/tmp/subversion-root/usr/lib/python2.3/site-packages/libsvn/_repos.la /var/tmp/subversion-root/usr/lib/python2.3/site-packages/libsvn/_wc.la + xargs -0 rm -f + find /var/tmp/subversion-root -type f -a '(' -name .packlist -o '(' -name '*.bs' -a -empty ')' ')' -print0 + find /var/tmp/subversion-root/usr/lib64/perl5 -type f -perm 555 -print0 + xargs -0 chmod 755 find: /var/tmp/subversion-root/usr/lib64/perl5: No such file or directory chmod: too few arguments Try `chmod --help' for more information. error: Bad exit status from /var/tmp/rpm-tmp.60766 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.60766 (%install) Version-Release number of selected component (if applicable): subversion-1.1.1-2.1 How reproducible: 100% Steps to Reproduce: 1. try to rebuild subversion RPM on an installed RHEL-4 powerpc machine Actual results: see attachment below for full build log.
Created attachment 117814 [details] full build.log
That looks like a broken build environment - it's getting libdir=/usr/lib64 for a ppc32 build? + ./configure --build=powerpc-redhat-linux-gnu --host=powerpc-redhat-linux-gnu --target=ppc-redhat-linux-gnu ... --libdir=/usr/lib64 ...
Toggled to private, yeah, I guess. Still: never should you have libdir=/usr/lib64 for a 32-bit ppc build. That just doesn't make sense.
This is either an rpm configuration issue or something; it needs more investigation to assign properly, either way. Can't reproduce on a RHEL4/ppc64 P5 box here: jorton@jupiter:~$ ppc rpmbuild --target ppc --eval %{_libdir} /usr/lib rpmbuild: no spec files given for build
The status NEEDINFO_QA has been deprecated in favor of NEEDINFO. Moving bugs to NEEDINFO.