Bug 1106271 - nc6: FTBFS in rawhide
Summary: nc6: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: nc6
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Šabata
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F21FTBFS
TreeView+ depends on / blocked
 
Reported: 2014-06-09 04:07 UTC by Dennis Gilmore
Modified: 2014-06-10 14:00 UTC (History)
3 users (show)

Fixed In Version: nc6-1.0-19.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-10 14:00:12 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (6.47 KB, text/plain)
2014-06-09 04:07 UTC, Dennis Gilmore 		no flags Details
root.log (81.37 KB, text/plain)
2014-06-09 04:07 UTC, Dennis Gilmore 		no flags Details
state.log (1.04 KB, text/plain)
2014-06-09 04:07 UTC, Dennis Gilmore 		no flags Details
Move the comments around a little (585 bytes, patch)
2014-06-10 13:59 UTC, Petr Šabata 		no flags Details | Diff
View All

Description Dennis Gilmore 2014-06-09 04:07:14 UTC 
Your package nc6 failed to build from source in current rawhide.

http://koji.fedoraproject.org/koji/taskinfo?taskID=6963851

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
Comment 1 Dennis Gilmore 2014-06-09 04:07:17 UTC 
Created attachment 904373 [details]
build.log
Comment 2 Dennis Gilmore 2014-06-09 04:07:19 UTC 
Created attachment 904374 [details]
root.log
Comment 3 Dennis Gilmore 2014-06-09 04:07:20 UTC 
Created attachment 904375 [details]
state.log
Comment 4 Petr Šabata 2014-06-10 13:37:43 UTC 
Running configure fails because the regenerated configure script is broken on line 3124:

 3122     as_fn_error $? "Your 'rm' program is bad, sorry." "$LINENO" 5
 3123   fi
 3124 fi           ac_config_headers="$ac_config_headers config.h"
 3125 
 3126
Comment 5 Petr Šabata 2014-06-10 13:59:48 UTC 
Created attachment 907271 [details]
Move the comments around a little
Note You need to log in before you can comment on or make changes to this bug.