-
Notifications
You must be signed in to change notification settings - Fork 118
guix openssl-sys-0_9_61_H1 run failure (was: bootstrapping 1.54.0 with mrustc parallel build failure) #343
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
Comments
The failure on However: |
Regarding the first problem, it gets build first here, I think:
Then later I see:
I'm attaching the complete build log. Regarding the second error, I doubt there's a problem with my file system; it's Btrfs on a NVMe drive; the build happens in its own container without access to the rest of the file system or network, and I don't see anything spelling trouble in I've tried to reproduce it and with 2 new builds so far haven't succeeded, so it's potentially difficult to trigger. |
Oh, but I see other similar reports by fellow Guix contributors in https://issues.guix.gnu.org/74142, complete with logs. |
And also https://issues.guix.gnu.org/57879 |
Please confirm that you are using the latest version of mrustc, as that log output doesn't match the output of the most recent version of minicargo (with the fixed job sequencing). There should be messages when each job is completed (e.g. |
I was able to reproduce on a 3rd build:
Full log attached. |
The log you originally posted claims to be for revision 1827564, but doesn't have |
Oh, it seems I borked my update of mrustc... was still using the v0.10.1 tag. I'll try again, probably resolved then :-). |
OK, now I'm confident I'm on the latest revision 1827564 (sorry for the earlier mishaps!), and could still trigger a failure:
Uploading rust-1.54.0-fail-with-mrustc-1827564.log… Build log attached. |
That build log link doesn't work, but it doesn't matter - as the error is within the build script this time.
The file |
The
Running the gcc command it contains succeeds (exit status 0). Hm. |
That gcc command is just from openssl calling "rustc" (actually Could you run the build script under gdb (remember to provide the correct environment, see the dump of environment variables in the log). A trick for making it easier to debug: Grab the
|
Also, could you check the |
Hello,
When building rust/cargo 1.54.0 with mrustc (latest commit, 1827564) I get:
That appears to be an issue with building with many cores (my machine uses -j32).
The text was updated successfully, but these errors were encountered: