-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
Allow gcc/gfortran 12 #33187
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Author: Matthias Koeppe |
Branch: u/mkoeppe/allow_gcc_gfortran_12 |
Commit: |
comment:5
So rejecting GCC 12 is justified. |
comment:6
Singular:
|
comment:7
Giac:
|
comment:8
I suppose we should update these two packages first and then see if the failures persist |
comment:9
Are you trying to compile |
comment:10
Yes, that's probably it |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:16
Tested using |
comment:17
The next error on
but that looks just like a broken system package |
comment:19
|
Reviewer: Dima Pasechnik |
comment:21
lgtm |
comment:22
Thanks! |
Changed branch from u/mkoeppe/allow_gcc_gfortran_12 to |
https://gcc.gnu.org/gcc-12/changes.html
fedora-36
(rawhide) just started to use GCC 12, which we reject. (https://github.com/sagemath/sage/runs/4860062925)On this ticket we change the
spkg-configure.m4
scripts to allow gcc/gfortran 12.We also add GCC 4.9.x (but not 4.8.x) to the reject list; this compiler was the reason to drop support for
debian-jessie
in #32947.Upstream PRs:
CC: @culler @dimpase @kiwifb @antonio-rojas
Component: packages: standard
Author: Matthias Koeppe
Branch/Commit:
f27ff17
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/33187
The text was updated successfully, but these errors were encountered: