Red Hat Bugzilla – Full Text Bug Listing
|Summary:||F15 glibc tzdata-update can't build on ARM|
|Product:||[Fedora] Fedora||Reporter:||Daniel Drake <dsd>|
|Component:||glibc||Assignee:||Jeff Law <law>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||15||CC:||jakub, ndevos, pbrobinson, schwab|
|Fixed In Version:||glibc-2.14.1-2||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2012-03-02 11:47:24 EST||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Daniel Drake 2011-10-03 12:13:51 EDT
Created attachment 526096 [details] glibc-tzdata-nonstatic.patch In bug #708452, F16 glibc was fixed to work on ARM. We're now building F15 for ARM and have hit one of the same issues - the tzdata-update.c compile issue (all the other issues mentioned in #708452 are already fixed in f15 - thanks!). The tzdata-update problem was fixed for F16 by removing all the arch-specific syscall definitions and just using glibc. Could this change please be backported to F15? I'm attaching a patch which takes tzdata-update.c from F15 form to F16 form. Also, if you're happy for me to commit this as a patch from the spec file for F15 (as one less distraction for you), I'm attaching a spec patch that I could commit to fix this bug. I've tested it on ARM and i686. Thanks!
Comment 2 Fedora Admin XMLRPC Client 2011-11-14 14:45:51 EST
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Comment 3 Fedora Update System 2011-12-19 02:50:59 EST
glibc-2.14.1-4 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/glibc-2.14.1-4
Comment 4 Fedora Update System 2012-01-02 12:04:48 EST
glibc-2.14.1-5 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/glibc-2.14.1-5
Comment 5 Fedora Update System 2012-01-17 15:24:28 EST
glibc-2.14.1-5 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
Comment 6 Peter Robinson 2012-03-02 11:47:24 EST