-
-
Notifications
You must be signed in to change notification settings - Fork 620
Build failure in Fedora 42 with gcc 15 #40047
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
Comments
At this point, i pulled the following
which solved the issue with singular by allowing the use of a system package. maxima will fail because of
Interestingly, maxima 5.47 itself, from the upstream(https://git.code.sf.net/p/maxima/code), will compile fine |
Applying the patch From 77ff9989ef7ccf261ad82c1c843686acd4eaec87 Mon Sep 17 00:00:00 2001
From: erentar
Date: Sun, 4 May 2025 14:43:15 +0200
Subject: [PATCH] planarity update
---
build/pkgs/planarity/checksums.ini | 7 ++++---
build/pkgs/planarity/package-version.txt | 2 +-
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/build/pkgs/planarity/checksums.ini b/build/pkgs/planarity/checksums.ini
index 3caec0cca3f..032b6245f57 100644
--- a/build/pkgs/planarity/checksums.ini
+++ b/build/pkgs/planarity/checksums.ini
@@ -1,4 +1,5 @@
tarball=planarity-VERSION.tar.gz
-sha1=8407bccf33c07bf0dae22d79b5e6ac7d89c62ea3
-sha256=63e979d37e7160e4e72a286a8dd7ba74e4795f63742f417c8ba1cea2b2a51280
-upstream_url=https://github.com/sagemath/sage-package/releases/download/tars/planarity-VERSION.tar.gz
+sha1=85574b846db77a2258d5ab5279464184990cb21e
+sha256=df3c86c32fd37b801079aea7de67675efdef12ada557cbcaae821e81b8db438d
+; upstream_url=https://github.com/sagemath/sage-package/releases/download/tars/planarity-VERSION.tar.gz
+upstream_url=https://github.com/graph-algorithms/edge-addition-planarity-suite/releases/download/Version_4.0.0.0/planarity-4.0.0.0.tar.gz
\ No newline at end of file
diff --git a/build/pkgs/planarity/package-version.txt b/build/pkgs/planarity/package-version.txt
index 9a2596b9e46..f69d48948a7 100644
--- a/build/pkgs/planarity/package-version.txt
+++ b/build/pkgs/planarity/package-version.txt
@@ -1 +1 @@
-3.0.1.0
+4.0.0.0
\ No newline at end of file
--
2.49.0 and configuring with |
See also #40038 which contains the changes I had to implement to have it compile on Fedora 42 (using meson, not sage-the-distro). |
I am not sure if it is the right way, but I needed to add gnu=17 to gap and sagelib; also to planarity, but it seems changing to the new version avoids this change. |
Build also fails on > gcc --version
gcc (GCC) 15.1.1 20250425
Copyright (C) 2025 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. |
If you apply the changes in #40033 it should work. |
Indeed, these changes also resolve the issues for |
I'm not sure how anyone is able to build successfully given ecl 24.5 (the latest version, also the current version on sage) is incompatible with it.
keywords According to #39977 (comment) this issue is being worked on, however the fix has not come in yet. |
Nevermind. I have misread the thread at #39977. |
Building from fresh with A jank way around this is to first build with I will provide a dockerfile soon The only successful build i have managed was with these commits https://github.com/erentar/sage/commits/fedora42fix1/ and issuing $ make configure
$ ./configure \
--with-system-ecl=no \
--with-system-singular=no \
--with-system-linbox=no
$ make -j $(nproc) build \
|| CFLAGS="-std=gnu17" make -j $(nproc) build |
What worked for me is in #39977 (comment) and modifying spkg-install.in for: gap, planarity, and sagelib. |
|
Uh oh!
There was an error while loading. Please reload this page.
Environment
I am opening this issue to consolidate the dialog currently ongoing on various pull requests.
Currently, pull requests relating to this problem are
Steps To Reproduce
Config log
singular will fail with
Package logs
No response
Additional Information
No response
Checklist
The text was updated successfully, but these errors were encountered: