Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi! I'm using
musl-cross-makefor a robotics project with the main executable in Rust and buildrootuwipias the OS.uwipiships Linux 5.10 which is an LTS kernel release.I needed Linux headers for my project, so I added 5.10 support locally. Here's a PR which adds the hash file for that release. You should double check the sha1sum, I just used what my machine checksummed from the archive when I downloaded it manually. I don't think I was being MITM'ed, but, you can never be too sure!
Thanks for this awesome project, it saved me a ton of time.
(If you got here by googling, note that Rust internally uses a 1.1.x MUSL release as of the time of writing. I had to specify away from
musl-cross-make's 1.2.x version manually in myconfig.makto avoid linker issues with__clock_gettime64!)