-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
stdenv: let aarch64 use gcc ≥10 #108305
Comments
I marked this as stale due to inactivity. → More info |
In #153329 adding |
🤔 changing stdenv to gcc11Stdenv doesn't work? |
True. That's a cleaner solution if it does work in your case. |
Another blocker: #191357 |
Another victim: #210859 |
Another victim: |
Potential solution: (If I may summarize what can be inferred from the issue page) |
FWIW the commit message and leading comment for #209870 both contain this text:
but for some reason github isn't processing it. |
Github is having a pretty bad day it seems, it'll probably catch up in a bit. |
Specifically, this PR doesn't show a "merging #209870 may close this bug" or list this as a "linked issue" of that PR. It should say "Development Successfully merging this pull request may close these issues: #209870" For an example of what it should look like, check out e.g. number 216163 (no hyperlink to avoid noise in that PR). |
Note to self: 6d6a980 will need to be reverted when any of the solutions land. |
@wegank Can you link the PR in which this was fixed? |
Describe the bug
Nixpkgs upgraded to gcc 10 in #89793. Unfortunately, there were issues with aarch64 so aarch64 still uses gcc 9.
The text was updated successfully, but these errors were encountered: