Here is some update about this issue: I've just built Sage 10.9.beta2 from a fresh git clone on a different computer, still running Ubuntu 24.04 without any system Maxima. The issue is still there. Then, on the same computer, I've also built Sage 10.8 from a fresh git clone and discovered that it has the same issue. I reported above that there is no issue in Sage 10.8, but this was with a Sage 10.8 resulting from *incremental* builds through the Sage 10.8.beta series. To summarize, on Ubuntu 24.04, the situation is the following one:
- Sage 10.7: OK - Sage 10.8 from incremental building: OK - Sage 10.8 and 10.9.beta2 built from scratch (fresh git clone): Maxima broken As this stage, one may suspect https://github.com/sagemath/sage/pull/40265 which was merged in Sage 10.8.beta8, since this is the major Maxima interface change in the 10.8.beta series. FWIW, in Sage 10.7, we have sage: from sage.env import MAXIMA, MAXIMA_FAS, MAXIMA_SHARE sage: MAXIMA '/home/eric/sage/10.7/local/bin/maxima' sage: MAXIMA_FAS '/home/eric/sage/10.7/local/lib/ecl/maxima.fas' sage: MAXIMA_SHARE '@SAGE_MAXIMA_SHARE@' while in Sage 10.9.beta2, we have sage: from sage.env import MAXIMA, MAXIMA_FAS, MAXIMA_SHARE sage: MAXIMA '/home/eric/sage/10.9/build/sage-distro/subprojects/maxima-5.47.0/dist/usr/local/bin/maxima' sage: MAXIMA_FAS '/home/eric/sage/10.9/build/sage-distro/subprojects/maxima-5.47.0/build/src/binary-ecl/maxima.fas' sage: MAXIMA_SHARE '/home/eric/sage/10.9/build/sage-distro/subprojects/maxima-5.47.0/dist/usr/local/share/maxima/5.47.0/share' Eric. Le mardi 6 janvier 2026 à 09:39:57 UTC+1, Eric Gourgoulhon a écrit : Le lundi 5 janvier 2026 à 14:18:07 UTC+1, [email protected] a écrit : Same error occurs on CI (after fixing another maxima-related error, that shadowed it before), see github.com/sagemath/sage/pull/40816#issuecomment-3699257180. Thanks for the link. What is dubious in the error message is Details: CL-INFO::LOAD-PRIMARY-INDEX: Cannot open #P"/usr/local/share/info/maxima-index.lisp". Since there is no system Maxima installed on my computer, nor on the CI runner I guess, there is nothing related to Maxima in /usr/local/share. Given that the standalone "sage -maxima" runs well (including the documentation), the question is why the Sage interface to Maxima is using the wrong path "/usr/local/share". Again, there was no such issue in Sage 10.8, which is built with the same version of the Maxima package. Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/c02e9946-7f8f-4708-b34d-6e75780f442bn%40googlegroups.com.
