Bug 749236 - FTBFS: xemacs fails to build in fedora rawhide
Summary: FTBFS: xemacs fails to build in fedora rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xemacs
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-26 14:43 UTC by Peter Schiffer
Modified: 2011-11-01 14:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-01 14:14:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Peter Schiffer 2011-10-26 14:43:15 UTC
Description of problem:
xemacs is failing to build in fedora rawhide

Version-Release number of selected component (if applicable):
xemacs-21.5.31-2.fc17

How reproducible:
always

Steps to Reproduce:
1. $ fedpkg clone xemacs
2. $ cd xemacs/
3. $ fedpkg scratch-build
  
Actual results:
from build.log:
Bootstrapping from temacs...
XEmacs: standard input is not a tty
make[1]: *** [NEEDTODUMP] Error 1

Expected results:
successful build

Additional info:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3461501

Comment 1 Jerry James 2011-10-31 16:56:36 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.


Note You need to log in before you can comment on or make changes to this bug.