Bug 749236
Summary: | FTBFS: xemacs fails to build in fedora rawhide | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Schiffer <pschiffe> |
Component: | xemacs | Assignee: | Jerry James <loganjerry> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | loganjerry, steve.traylen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-11-01 14:14:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Peter Schiffer
2011-10-26 14:43:15 UTC
This appears to have been due to the (now infamous) glibc-2.14.90-13 release. Those logs indicate that XEmacs had gone totally mad. It's behavior makes no sense at all. A scratch build today against glibc-2.14.90-15 completed normally. There must have been some really interesting code motion going on. I see that the merge of the f17-gmp tag is underway. I'll wait until that is done and then kick off one more xemacs build. But I have a concern. Was *everything* in f17-gmp built against glibc-2.14.90-13? If so, I hate to say it, but you'd probably better build the whole set of packages yet again. There may be all kinds of weird behavior lurking in those builds. |