This repository has been archived by the owner on Feb 28, 2023. It is now read-only.
Trying to build - zlib is not available #12
Comments
|
Hmm, that's interesting. It looks to me like there's an issue with the bootloader. I'm in the process of upgrading nebulet to use a more up-to-date version of the bootloader and that'll likely end up fixing this issue. Also, @phil-opp might know something. |
|
That does seem fairly likely to fix it. Trying to build bootloader from master on github works fine, trying to build it from the version in |
|
I think the problem is japaric/xargo#215: To work around this, you can remove the |
|
That lets it build! After running I assume this isn't intended behaviour? Particularly since it continues with the flashing black even if I replace the contents of |
|
Yes, the issue is that you're trying to boot with a bootloader version that's too new. I'm in the process of updating nebulet for upstream bootloader. That should be finished today, assuming my pr is merged into the upstream x86_64 crate by @phil-opp. After that, nebulet should boot just fine. |
|
@gmorenz Almost ready! It's just stuck on the new x86_64 crate being published so that the os_bootinfo crate can retrieve the new version. |
|
@gmorenz Nebulet is up and running! Give it a try! |
|
Same error as before, here's the output of a clean build (after pulling changes, and installing a fresh bootimage in case that had been updated too). I notice that it is using the most recent x86_64 and bootloader. What environment are you using that it succesfully builds under? |
|
Looked at your Edit: In trying to use |
|
To use the lld shipped with rustc, you have to delete the |
|
Give it another try now. |
|
I got it working by checking out the most recent code and undoing the change to Using the new |
|
That's really strange. Could it be isolated to Rrch Linux? I'm personally running Ubuntu in WSL. |
|
I doubt it's isolated to specfically arch linux just because arch tries to change so little from upstream packages. But I could easily imagine it's isolated to my system or non-debian-derivatives or some other category. Basically I think the problem is that rust's Supporting this is that by checking by I'll spend a bit of time later today and see if I can figure out how to make lld not try and use zlib, but I think there is a good chance that the best solution (i.e. not doing something like disabling debug info) is going to be to use the systems lld. |
|
Using rust's I'll switch it back to the system allocator for now. |
|
Using the current master branch and rustc's
The keyboard interrupt occured when I pressed the escape key. |
|
Just an update that I still experience the zlib issue (error message: For anyone else who experiences this issue. The workaround is |
gmorenz
changed the title
|
Hmm, there's no file called |
|
Oops, that's a local file I made the first time around I guess... here is a copy of it for anyone who needs it: |
|
I'm kind of surprised that works, since cretonne checks the |
|
Interesting... changing the os to nebulet (making the diff only changing |
|
Using Manjaro linux I also need to edit
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Update: See comment at bottom of issue.
I'm trying to build this, following the instructions in the readme.
I'm running a completely up to date version of Arch Linux (as of Fri April 13 - 10:00pm est). I also just updated rust (default rustc is nightly from 2018-04-11), and just used cargo to install
xargoandbootimage.I get the following error on
bootimage buildand I'm not sure what to do nextThe text was updated successfully, but these errors were encountered: