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
musl: 1.1.19 -> 1.1.20 #46064
musl: 1.1.19 -> 1.1.20 #46064
Conversation
Success on aarch64-linux (full log) Attempted: musl Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: musl Partial log (click to expand)
|
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: musl Partial log (click to expand)
|
I have fixes/cleanup for packages impacted by this when building musl-native, but even so they're minor (and often are the things we'll be doing for glibc 2.28 re:memfd_create, I believe) and been using this in my own work and LGTM. |
cc NixOS/rfcs#23 (subscribers to that may be interested in testing/feedback here--even post-merge). |
@dtzWill seems to break GCC for me: nh2/static-haskell-nix#6 |
FWIW another bump on the way: #54440 -- LMK if you end up testing it, problems or no :). |
Announcement: http://www.openwall.com/lists/musl/2018/09/04/17
Release commit (adds release notes to WHATSNEW): https://git.musl-libc.org/cgit/musl/commit/?h=v1.1.20&id=0fa1e638e87cf257e9f96b4019b2076afd674a19
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)The hydra instance powering my musl build-fleet died a few weeks ago
and as a result I haven't tested the impact this has on all-the-things
(esp in terms of various cross-compilation scenarios).
Many of these fixes are worthy of having been picked but it always
seemed a release was happening soon... :D
See the notes and commit logs for more details.