-
-
Notifications
You must be signed in to change notification settings - Fork 15k
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
[WIP] Build nixpkgs with gcc 8 by default #63132
Conversation
Unfortunately it will need some work, probably a rebase after the months. |
@vcunat Do you intend to work on this? Otherwise I'd like to try to do the rebase. |
I do not, at least not immediately. |
Rebased. Here is the jobset on Hydra: https://hydra.nixos.org/jobset/nixpkgs/gcc8 |
BTW, gcc 9 should be already viable as well. Whole Fedora has switched months ago. Still, it might be easier to do these steps separately, for better grouping of similar problems. |
I'd like to help with this PR, I hope there is still a chance for 19.09.
|
For qt4: we could reuse the AUR patch: https://aur.archlinux.org/cgit/aur.git/plain/qt4-gcc8.patch?h=qt4, or do |
llvm should already be fixed thanks to #63928. |
doesn't support gcc 8
gcc 8 support
This is now in staging-next. |
No, it isn't, at least not the current version e729736 :-/ Bitten by the rebasing workflow? |
As I'm against history-rewriting on staging-next, I suggest we merge this commit to staging-next and have a careful look at the conflicts and the overall merge result. |
Seems we have a gcc8 and gcc-8 branch. I merged the gcc8 branch instead of this gcc-8. |
Bad luck; first GitHub decided it got merged even if it didn't, and now this naming confusion. |
Reopened #53760