Summary: | =dev-lang/ghc-7.10.2 still occasionally crashes in parallel builds | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Freddie Witherden <freddie> |
Component: | Current packages | Assignee: | Gentoo's Haskell Language team <haskell> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | freddie, jstein, tetromino |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Emerge --info
Build log of ghc-7.10.2 |
Description
Freddie Witherden
2015-08-02 12:27:33 UTC
When attempting to upload the log file I get an access denied error. Will attempt to upload again later. It's possibly a parallel make error. As a gross workaround you can retry a build a couple of times or run as MAKEOPTS=-j1. (In reply to Sergei Trofimovich from comment #2) > It's possibly a parallel make error. As a gross workaround you can retry a > build > a couple of times or run as MAKEOPTS=-j1. Thanks, emerging with MAKEOPTS=-j1 worked. I can confirm that this solved the issue for me also. Perhaps the ebuild should force this? Created attachment 413288 [details]
Emerge --info
Created attachment 413290 [details]
Build log of ghc-7.10.2
-j1 didn't work for me. Looks like something wrong with haddock:
compiler/ghc.mk:655: recipe for target 'compiler/stage2/doc/html/ghc/ghc.haddock' failed
make[1]: *** [compiler/stage2/doc/html/ghc/ghc.haddock] Killed
(In reply to anrock623 from comment #6) > Created attachment 413290 [details] > Build log of ghc-7.10.2 > > -j1 didn't work for me. Looks like something wrong with haddock: > compiler/ghc.mk:655: recipe for target > 'compiler/stage2/doc/html/ghc/ghc.haddock' failed > make[1]: *** [compiler/stage2/doc/html/ghc/ghc.haddock] Killed compiler/ghc.mk:655: recipe for target 'compiler/stage2/doc/html/ghc/ghc.haddock' failed make[1]: *** [compiler/stage2/doc/html/ghc/ghc.haddock] Killed Suggests you has an OOM (try to check dmesg) or something external killing 'haddock'. *** Bug 533990 has been marked as a duplicate of this bug. *** |