Red Hat Bugzilla – Bug 997531
FTBFS: "Revert `Move to /usr' transition" broke builds on PPC
Last modified: 2016-11-24 07:21:57 EST
Description of problem:
+ cmp -s rtkaio/librtkaio.so ../build-ppc-redhat-linux/rtkaio/librtkaio.so
+ cp -a rtkaio/librtkaio.so /builddir/build/BUILDROOT/glibc-2.17.90-14.fc20.ppc/lib/rtkaio/../librtkaio-2.17.90.so
+ ln -sf librtkaio-2.17.90.so /builddir/build/BUILDROOT/glibc-2.17.90-14.fc20.ppc/lib/rtkaio/../librt.so.1
+ mkdir -p /builddir/build/BUILDROOT/glibc-2.17.90-14.fc20.ppc/lib/power6x
+ pushd /builddir/build/BUILDROOT/glibc-2.17.90-14.fc20.ppc/lib/power6x
+ ln -sf '../power6/*.so' .
+ cp -a '../power6/*.so.*' .
cp: cannot stat '../power6/*.so.*': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.n7eaaa (%install)
Bad exit status from /var/tmp/rpm-tmp.n7eaaa (%install)
Child return code was: 1
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ppc-koji build --scratch f20 glibc-2.17.90-13.fc20.src.rpm
(In reply to Karsten Hopp from comment #0)
> Description of problem:
> + librtkaioso=librtkaio-2.17.90.so
> + cmp -s rtkaio/librtkaio.so ../build-ppc-redhat-linux/rtkaio/librtkaio.so
> + cp -a rtkaio/librtkaio.so
> + ln -sf librtkaio-2.17.90.so
> + mkdir -p /builddir/build/BUILDROOT/glibc-2.17.90-14.fc20.ppc/lib/power6x
> + pushd /builddir/build/BUILDROOT/glibc-2.17.90-14.fc20.ppc/lib/power6x
> + ln -sf '../power6/*.so' .
> + cp -a '../power6/*.so.*' .
> cp: cannot stat '../power6/*.so.*': No such file or directory
> error: Bad exit status from /var/tmp/rpm-tmp.n7eaaa (%install)
> Bad exit status from /var/tmp/rpm-tmp.n7eaaa (%install)
Thanks, looking into this.
Still not resolved. Will get back on this on Monday.
Patch in testing.
Should be fixed now. Tested and fixed build on ppc64 system.
Kicked off build on primary arches:
Author: Carlos O'Donell <email@example.com>
Date: Thu Aug 29 00:36:52 2013 -0400
Fix Power build (#997531).
How can I force the ppc-koji instance to build something before waiting for it to pickup the primary build as a shadow build?
`ppc-koji build f21 ./path/to/final.src.rpm?'
Only koji admins are allowed to build from a srpm, and fedpkg has no support for secondary archs. But you can build from git like this:
ppc-koji build f21 `fedpkg giturl`
I've changed the version to f20, this bugzilla was opened before the f20 branching and that's where we need the fixed glibc.
I've tried a scratch build and noticed that you wouldn't be able to build the new glibc because some other package needs to build first (with the new glibc in the buildroot), a nice dependency loop. So I took the liberty and merged your patch into f20, it looks simple enough to not mess up anything on primary and built it on PPC and primary.
Thanks a lot !
(In reply to Karsten Hopp from comment #7)
> Hi Carlos,
> Only koji admins are allowed to build from a srpm, and fedpkg has no support
> for secondary archs. But you can build from git like this:
> ppc-koji build f21 `fedpkg giturl`
Thanks, that's what I was looking for.
> I've changed the version to f20, this bugzilla was opened before the f20
> branching and that's where we need the fixed glibc.
Right I was going to put this into f20 once I had confirmation that it really did fix things (I expected it to because I built it by hand on a ppc system)...
> I've tried a scratch build and noticed that you wouldn't be able to build
> the new glibc because some other package needs to build first (with the new
> glibc in the buildroot), a nice dependency loop. So I took the liberty and
> merged your patch into f20, it looks simple enough to not mess up anything
> on primary and built it on PPC and primary.
> Thanks a lot !
... but you've already put the patch into f20, which is fine. It's a tiny patch and a minor mistake on my part. I wasn't building the additional runtimes during testing to avoid the overhead.
It also looks like everything built correctly...
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version'
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.