Summary: | dev-haskell/http-4000.3.14 setup build failed with 'evacuate: strange closure type 0' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Harley Wiltzer <harleyw> |
Component: | Current packages | Assignee: | Gentoo's Haskell Language team <haskell> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Output of emerge --info "=dev-haskell/http-4000.3.14"
Build log |
Description
Harley Wiltzer
2019-12-15 16:12:11 UTC
Created attachment 599660 [details]
Build log
Yes, it's usually a low-level memory corruption on haskell heap. Might be a GHC bug, external C library bug or hardware memory corruption. If you try to build dev-haskell/http a few times does it fail in a similar way? Do you observe similar error on other haskell packages? (In reply to Sergei Trofimovich from comment #2) > Yes, it's usually a low-level memory corruption on haskell heap. Might be a > GHC bug, external C library bug or hardware memory corruption. > > If you try to build dev-haskell/http a few times does it fail in a similar > way? Do you observe similar error on other haskell packages? Hmm, I hadn't thought of just trying to build it a few times, but turns out that worked :) Successfully built dev-haskell/http-4000.3.14, followed by dev-haskell/cabal-install, app-text/pandoc, and dev-haskell/pandoc-citeproc, all without issues. Thanks for the help! I tried to build http in a loop for a a few hundred times and got no failures. Closing as WORKSFORME. I suggest to check you RAM with sys-apps/memtest86+ (or something similar) to rule out simple bit flip hardware corruption. Those are very nasty. |