Bug ID 1020909
Summary Big number of ghc* build failures in openSUSE:Factory
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Other
Assignee bnc-team-screening@forge.provo.novell.com
Reporter dimstar@opensuse.org
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

ghc-* packages have been quite painful from the beginning on (the deps seem to
be very strict based on build ids, which keep on changing on rebuilds - hence
always an entire tree needs to be built - terrible situation with the number of
ghc* packages increasing as it does)

But lately, this has turned out even worse: ~ 33% oif all ghc packages seem to
be in status failed by now in openSUSE:Factory

A typical build log contains plenty of:

>[   53s] /tmp/ghc1490_0/ghc_40.s:1795:0: error:
>[   53s]      Error: junk at end of line, first unrecognized character is `1'
>[   53s] 
>[   53s] /tmp/ghc1490_0/ghc_40.s:1803:0: error:
>[   53s]      Error: number of operands mismatch for `mov'
>[   53s] 
>[   53s] /tmp/ghc1490_0/ghc_40.s:1803:0: error:
>[   53s]      Error: junk at end of line, first unrecognized character is `1'
>[   53s] 
>[   53s] <no location info>: error:
>[   53s]     `gcc' failed in phase `Assembler'. (Exit code: 1)
>[   53s] error: Bad exit status from /var/tmp/rpm-tmp.dj6Wjl (%build)

Please help in correcting this issue and getting ghc somewhat back in usable
state.


You are receiving this mail because: