-
Notifications
You must be signed in to change notification settings - Fork 145
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 error on Linux #1206
Comments
I've got |
The error is probably saying the bitcode file written in the previous line doesn't exist. Dunno what could be causing that. You can get a better error and probably an actual backtrace by having |
Thank you for your response. I'm getting the same error as before with
Is there anything I can use at the |
You should probably check whether the file at issue (blablabla/min-start.bc) does exist at that time. I don't know why it wouldn't, but that's probably what the error is saying. |
The backtrace via :b doesn't look too useful, but I've included it below. The file
|
I seem to be able to generate
and then the following in the REPL:
|
If I copy that file to the right location the build seems to progress further until failing at the next step. Any ideas?
|
@Bike Ok, I think I've finally figured something out! If I change this line to I think when I'd be glad to submit a PR if you can confirm what needs to be changed. Also the build now fails at the
|
Maybe try just removing the |
Thanks, I was already experimenting with different values for it: setting it to I guess it would be helpful for the config templates to advertise this in one way or another. Currently comments in Maybe configure shouldn't even accept them either. Now that I finally got the build working, the debugger seems to be crashing... I guess I'll give up for today :)
|
Yeah, I think that build option documentation is old, sorry. The actual default is faso I think. The backtraces are because we have trouble specifically with that kind of error, since it's mediated by a POSIX signal handler. Other conditions should have backtraces fine. As in #961 and you already filed #1030. It's very unfortunate, but tricky to debug since we kind of want to throw an exception from a signal handler, which is necessarily undefined behavior in C/C++/POSIX. |
Right, regarding #1030: I assumed it was an issue on BSD only, thanks for the clarification. I think we can close this issue, although I'd like to submit a PR for updating the configuration templates so others don't run into this in the future. Thank you for your help with debugging the build. |
I've also encountered some issues building main (3ec388b) on Linux (Arch Linux).
Config:
I'm using the following for LLVM13:
https://aur.archlinux.org/packages/llvm13/
I'm using the gold linker because the above package doesn't seem to ship with lld and using the system lld results in a segmentation fault.
The error seems to be the following:
Full build logs are available here.
The text was updated successfully, but these errors were encountered: