Pipeline is broken with current rust nightly. #7
Comments
jschwe
changed the title
jschwe
added a commit
to jschwe/rusty-hermit
that referenced
this issue
May 6, 2020
Building release version with lto optimization fails with nightlies after 2020-04-29, so we just use that one for now.
jschwe
added a commit
to jschwe/rusty-hermit
that referenced
this issue
May 6, 2020
Building release version with lto optimization fails with nightlies after 2020-04-29, so we just use that one for now.
jschwe
added a commit
to jschwe/rusty-hermit
that referenced
this issue
May 6, 2020
Building release version with lto optimization fails with nightlies after 2020-04-29, so we just use that one for now.
|
Yes, I am able to reproduce the problem. I think that we have to disable LTO for the release version. Afterwards it works on my system. |
|
@stlankes Could you also merge this into the devel branch? Also would you like to keep this issue open, or should we create a new issue for figuring out why LTO doesn't work anymore? |
|
Hm, a new issue will be great. I will cherry-pick the PR and merge it to the branch devel. |
|
The Pipeline works again since LTO has been disabled for now. Closing this issue. Further discussion of the LTO problem in #15 |
ryan-jacobs1
pushed a commit
to cs360v8/rusty-hermit
that referenced
this issue
Sep 24, 2020
Fix loader. Previously strongly dependent on the input ELF's layout.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm currently working on hermit-os/kernel#40 and I just can't get the pipeline to work. Compiling (rusty_demo) always fails at the last step with
error: failed to get bitcode from object file for LTO (Bitcode section not found in object file)This error is also present in the gitlab ci pipeline. At first I couldn't reproduce this issue on my machine.
But after updating my rust nightly I now also run into this issue on my machine.
nightly-x86_64-unknown-linux-gnu updated - rustc 1.45.0-nightly (7ced01a73 2020-04-30) (from rustc 1.44.0-nightly (45d050cde 2020-04-21))Can anyone else reproduce this?
The text was updated successfully, but these errors were encountered: