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
llvmPackages: 5 -> 7 on Linux, keep Darwin at 5 until fixed #49402
Conversation
My previous attempts to bump the Darwin stdenv version didn't seem to work, but AFAIK doing so should be straightforward for anyone with a Darwin builder and the interest in tackling this. While not the preferred solution, adding a conditional lets us move on, as we missed 6 entirely due to no one getting around to resolving the Darwin bootstrap accordingly.
A miscompilation bug was mentioned on the other PR, it may be wise to check if LLVM 7 contains the fix (although this would mostly impact Darwin). |
Failure on x86_64-darwin (full log) Attempted: mesa Partial log (click to expand)
|
Timed out, unknown build status on x86_64-linux (full log) Attempted: mesa Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: mesa Partial log (click to expand)
|
Anyone have thoughts -- particularly "please wait"-- on this? |
I don't really see a reason to diverge. I would propose to drop libxml2 by default and switch everything or nothing. The darwin builds will also give us a better overview of the impact. |
Are there any issues on darwin? This would help us out because llvm 7 contains dsymutil which is needed to fix #52148. |
We have to disable (libxml?) on darwin, or just by default to avoid bootstrapping problems. |
Beep boop, ping! O:)
…On Sat, 15 Dec 2018 12:04:30 -0800, Daiderd Jordan ***@***.***> wrote:
We have to disable (libxml?) on darwin, or just by default to avoid bootstrapping problems.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#49402 (comment) part: text/html
|
This pull request has been mentioned on Nix community. There might be relevant details there: https://discourse.nixos.org/t/nixos-19-03-feature-freeze/1950/5 |
I can hardly guess the amount of breakage, but I'd hope almost all will be built-time. It might be worth creating a separate x86_64-linux -only jobset on Hydra just for this, so that these regressions get separated from others. |
Just as an FYI, I tried LLVM 7 with Mesa on NixOS Unstable and I get the following errors when trying games from Steam Proton (might be unrelated):
I'm trying LLVM 7 by using the following (this also could be completely wrong, I'm new to NixOS!):
LLVM 6 works fine. |
Let's aim for this right after the 19.03 branch off. We still have quite a few things in staging that I am wanting to prioritize. |
Sounds good for me! Thanks for making these calls! o7 (salute)
…On Tue, 05 Feb 2019 16:19:04 -0800, Matthew Bauer ***@***.***> wrote:
Let's aim for this right after the 19.03 branch off. We still have quite a few things in staging that I am wanting to prioritize.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#49402 (comment) part: text/html
|
Replaces #39986.
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)I've been using 7 as my default for over a month (ea00916)
and so far so good -- although my usage certainly doesn't cover all packages impacted by this.