-
-
Notifications
You must be signed in to change notification settings - Fork 522
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
configure: Accept gcc/gfortran 10.x #29456
Comments
comment:3
Any more details on palp? |
comment:4
Also, if we are targeting 9.2 we can move to higher scipy. |
comment:5
Replying to @kiwifb:
For example here: https://github.com/mkoeppe/sage/runs/618646432?check_suite_focus=true |
comment:6
Replying to @kiwifb:
As far as I can see there is no release yet with the fix |
comment:7
Question is whether we want to fix this for 9.1 already. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:10
Presumably Fedora 32 has patched packages. |
This comment has been minimized.
This comment has been minimized.
comment:12
Replying to @mkoeppe:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:19
Besides the packages cited in the description (cannot say about gf2x) gap_packages does not build, due to cohomolo package. |
comment:20
Palp 2.11 mentions gcc 10 compatibility:
|
comment:21
Unfortunately I'm not sure if the upstream source tarball for palp 2.11 is finalized though. Since I've packaged it 3 days ago (NixOS/nixpkgs#87944) the tarball silently changed. |
comment:22
Replying to @timokau:
I just adopted the patch already shipped in fedora until a new release.
|
comment:23
For what it's worth, upstream confirmed that palp 2.11 is stable and no further changes are expected. |
Changed keywords from none to sd109 |
This comment has been minimized.
This comment has been minimized.
comment:25
I have opened #29859 for |
This comment has been minimized.
This comment has been minimized.
comment:41
Tests running at https://github.com/mkoeppe/sage/actions/runs/168165380 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
comment:49
Re-enabled gcc 10. Tests run at https://github.com/mkoeppe/sage/actions/runs/199625493 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:51
I have just built it successfully. It failed the installation of gap_packages because of package cohomolo but it also fails to compile in gap itself. |
comment:52
Thanks for testing! If there's no ticket for gap_packages yet, could you open one please? |
comment:53
Replying to @mkoeppe:
I just opened gap-packages/cohomolo#24 |
This comment has been minimized.
This comment has been minimized.
Author: Matthias Koeppe |
Reviewer: Volker Braun |
comment:57
Thanks. |
comment:58
Replying to @vbraun: FWIW, worked for me for the upgrade to 9.2.beta9... |
comment:60
this seems not to be in beta9, right? should it be in beta10? |
Changed commit from |
As all build errors of standard packages with gcc/gfortran 10 have been fixed, we change the
gcc
andgfortran
configure scripts to again accept these versions.This ticket does not change the version of the gcc spkg.
Previous tickets:
fedora-32-minimal
gfortran
spkg-configure: Reject versions >= 10Related discussions:
Depends on #3360
Depends on #29766
CC: @dimpase @orlitzky @kiwifb @vbraun @enriqueartal @alexjbest @heluani @EmmanuelCharpentier
Component: porting
Keywords: sd109
Author: Matthias Koeppe
Branch:
c898920
Reviewer: Volker Braun
Issue created by migration from https://trac.sagemath.org/ticket/29456
The text was updated successfully, but these errors were encountered: