-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build Failure #76
Comments
And what should I see in this blurb? I have no problem to compile it, so you'll have to provide more information, the environment, the command line used to generate the build log, etc, etc... |
I replied on the gist, but I should have replied here: To my eyes there are only two interesting lines in the whole log:
With ghc the exit failure number typically corresponds to a unix signal number. In this case, it should correspond to SIGKILL. Normally GHC complains about the impossible when it fails an assertion. To me, this looks like someone or something used |
the -9 could be a symptom of a out-of-memory kill, but without more information, it's hard to tell :-/ |
In my experience out of memory (with ghc) always shows up as 11 (segfault). |
It must be out-of-memory kill cause I noticed ghc taking up 3.8 GB of system ram and 3 GB of Swap and die then. |
I've attached the build log
https://gist.github.com/xavier83/11f98d538bc5b4e5863a
The text was updated successfully, but these errors were encountered: