ghc6 6.8.2-1ubuntu1 FTBFS on sparc

Bug #194912 reported by StefanPotyra
4
Affects Status Importance Assigned to Milestone
ghc6 (Ubuntu)
Fix Released
Undecided
StefanPotyra

Bug Description

Binary package hint: ghc6

LP build log: http://launchpadlibrarian.net/11902091/buildlog_ubuntu-hardy-sparc.ghc6_6.8.2-1ubuntu1_FAILEDTOBUILD.txt.gz

strange enough, the build was killed...

currently trying on spooky (TI UltraSparc II (BlackBird)), currently at the same positions (build duration on that box some 20 hours to now, still building).

top:
23688 root 25 0 210m 208m 4184 R 98 12.9 293:48.82 cc1

StefanPotyra (sistpoty)
Changed in ghc6:
assignee: nobody → sistpoty
status: New → Confirmed
Revision history for this message
StefanPotyra (sistpoty) wrote :

hm... seems to have a different position (the output is confusingly similar)... still building (>= 24 hours) now and making progress.

Revision history for this message
Michael Bienia (geser) wrote :

Perhaps asking the buildd admins to increase the timeout for ghc6 on sparc helps if your test build succeeds.

Revision history for this message
StefanPotyra (sistpoty) wrote :

hm... still building... *g*.

Yes, asking infinity is on my TODO list:

<sistpoty> lamont: oh... any chance, to increase that timeout? (it does some heavy ghc6 -> c-file -> gcc things, which really
take a long time for gcc to be done with one file (at least on the test box I'm using right now)
<lamont> sistpoty: yes.. poke infinity on mondya

Revision history for this message
StefanPotyra (sistpoty) wrote :

Yep, the build just finished, seems like there are no other problems beside it being killed prematurely.

sudo chroot hardy-chroot bash 201566.65s user 4853.01s system 99% cpu 57:25:57.17 total

Revision history for this message
StefanPotyra (sistpoty) wrote :

For the record, there is one ghc6->gcc call, where gcc took about 800 minutes to complete (w.o. producing output) on spooky.

Revision history for this message
StefanPotyra (sistpoty) wrote :
Changed in ghc6:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.