-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Support system installations of ECL and fix the kenzo SPKG build #29617
Comments
To be copied as build/pkgs/ecl/spkg-configure.m4 |
Attachment: ecl_spkg-configure.m4.gz Attachment: maxima_spkg-configure.m4.gz To be copied as build/pkgs/maxima/spkg-configure.m4 |
comment:1
Note: I also tried to use only ECL from the system packages, and build maxima from Sage, but in this case Maxima fails
|
comment:2
I would wait for #22191 before attempting this if I were you. We have a mountain of patches for ecl-16.1.2 that won't be present in any system copy, and ecl-16.1.3 is incompatible with sage (that's why we haven't upgraded to it after so many years). The latest v20.4.24 release is from just a few days ago, though, and with any luck it will work (unpatched) with sage and we can look for v20.4.24 on the system. |
comment:3
OK, in FreeBSD the ECL system package is at 16.1.3! I did not know that it was incompatible with sage, maybe this is the source of the problem, thanks. |
Dependencies: #22191 |
comment:5
Note: applying patches from build/pkgs/ecl/patches and build/pkgs/maxima/patches to the FreeBSD ports, I have been able to use them as system packages. For ECL 16.1.3, the patches from #22191 are required. |
comment:6
perhaps one can get FreeBSD's ECL bumped to v20.4.24 ? Well, we do ship a lot of patches for it in #22191 - but they are all upstream patches. |
Changed author from gh-thierry-FreeBSD to Thierry Thomas |
New commits:
|
Changed author from Thierry Thomas to Thierry Thomas, Dima Pasechnik |
Commit: |
Branch: u/dimpase/packages/eclconfig |
comment:9
It appears that perhaps Gentoo's |
comment:11
I'm not an ecl maintainer, so we will probably have to wait for the next point release of ecl to address all of the bugs that sage fixes with patches. Afterwards the spkg-configure.m4 should check for a version newer than that patch release. If we add this spkg-configure now, we're going to be in a position similar to the one we were in with pari a few months ago. The upstream release is unsuitable, so we need to test for all of the bugs fixed by the custom patches so that we don't accept a distro version that's missing them. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:75
is kenzo build fixed? I'm getting (on macOS/homebrew), with ecl from Homebrew
|
comment:77
Replying to @miguelmarco:
It fixes the build for my system ECL (with ASDF unbundled). If it also works with sage's ECL spkg, I think we have a solution. Thanks! |
comment:78
I just made a new release. You can get the tarball at https://github.com/miguelmarco/kenzo/releases/download/1.1.10/kenzo-1.1.10.tar.gz Please check that it solves the problem, and then we can update the kenzo Sage package. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
comment:80
The kenzo upgrade is now included, and my previous broken spkg-install hack removed. Everything still works with system ECL. Github has helpfully disabled actions on my account after the last run, and I'm waiting to hear back from support. Can someone else kick off a CI run please? |
comment:81
Running at https://github.com/mkoeppe/sage/actions/runs/732049335 (with a bunch of other tickets) |
Changed reviewer from https://github.com/mkoeppe/sage/actions/runs/732049335 to Matthias Koeppe |
comment:82
One of the bunch of tickets was broken; the failures that you see in the run are from that. A new run is at https://github.com/mkoeppe/sage/actions/runs/733869032: Correctly accepts system ecl on Correctly accepts system ecl on Correctly accepts system ecl on Correctly rejects too old system ecl on other platforms. Build of |
Changed branch from u/mjo/ticket/29617 to u/mkoeppe/ticket/29617 |
This comment has been minimized.
This comment has been minimized.
New commits:
|
Changed branch from u/mkoeppe/ticket/29617 to |
I tried to use ECL and Maxima from system packages as suggested by #27330, but without success for the moment.
The
spkg-configure.m4
are trivial (see attachments), but the problems occur during build:In [dochtml] [manifolds] this error is produced:
Actually this error is reproducible out of the Sage's build mechanism:
According to Maxima's code,
set-locale-subdir
is defined insrc/init-cl.lisp
and:Maybe someone with Lisp-fu could patch it, if possible?
Depends on #31593
CC: @orlitzky @kiwifb @antonio-rojas @spaghettisalat @tobiasdiez @isuruf @mkoeppe @miguelmarco @jhpalmieri @jcuevas-rozo @slel @vbraun
Component: build: configure
Keywords: ECL, Maxima
Author: Thierry Thomas, Dima Pasechnik, Michael Orlitzky
Branch/Commit:
5cbe423
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/29617
The text was updated successfully, but these errors were encountered: