Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1098327
Summary: | glibc-2.19.90-15.fc21 broken on aarch64 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Robinson <pbrobinson> |
Component: | glibc | Assignee: | Kyle McMartin <kmcmartin> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | urgent | ||
Version: | rawhide | CC: | codonell, fweimer, jakub, kmcmartin, law, pbrobinson, peterm, pfrankli, spoyarek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | aarch64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glibc-2.19.90-16.fc21 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-05-26 08:00:28 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 922257 |
Description
Peter Robinson
2014-05-15 19:51:54 UTC
(In reply to Peter Robinson from comment #0) > glibc-2.19.90-15.fc21 had broken the build root on aarch64 The -15 update is a pull of new upstream changes between April 29th and May 15th. Can you confirm that -14 works? Is the mock chroot completely broken or can you login to it? Anything you can do to narrow down the failure helps. -14 is fine and once we untagged -15 all is back to building OK. I don't have access to the builders to be able to login to chroot, but as chroot creation doesn't complete I'm not sure how usable it would be (In reply to Peter Robinson from comment #2) > -14 is fine and once we untagged -15 all is back to building OK. > > I don't have access to the builders to be able to login to chroot, but as > chroot creation doesn't complete I'm not sure how usable it would be Alright I'm building the latest upstream glibc and I'll see what the testsuite does. I think this is fixed, but I have no idea why... testing now. I'm unable to reproduce this after backporting a patch from master. Building now (and it should go away in the next bi-weekly rebase?) --Kyle This turns out to have been caused by: commit 2fbdf5339aaeaa423bd661524f7ec7af41fa2606 Author: Roland McGrath <roland.com> Date: Wed May 14 11:06:36 2014 -0700 Consolidate not-cancel.h files. which resulted in some changed syscall definitions in libio, resulting in this weird bug. Fun. Anyway, fixing the notcancel syscall prototype resolves it. (I also did a -17 build which has some upstream-candidate TLS fixes as well.) regards, Kyle I've rebased rawhide now. |