Sage 10.9 released

142 views
Skip to first unread message

Volker Braun

unread,
May 4, 2026, 6:45:36 PM (13 days ago) May 4
to sage-release
The "master" git branch has been updated to Sage-10.9. As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html

There was no change over 10.9.rc2


John H Palmieri

unread,
May 5, 2026, 1:05:28 PM (13 days ago) May 5
to sage-release
I'm curious: why release 10.9 when it doesn't build out of the box on OS X?

Volker Braun

unread,
May 5, 2026, 6:36:10 PM (12 days ago) May 5
to sage-release
I checked that there is no open blocker issue, and then made the release. I didn't read the details of all mailinglist threads.

Sage doesn't build "out of the box" on OSX for some time now. 

There is the conda install which I guess works (haven't tried) but doesn't let you do local development.

There is the system-wide (root-ful) homebrew which is tested on the CI, there is going to some combination of homebrew packages that lets you build the rest of Sage? 

On my Mac I need a pristine environment so I don't really want to install homebrew system-wide, and there I've still not managed to build Sage. Granted I didn't have much time recently, it looks possible. But its definitely playing on hard mode.

IMHO not being able to easily build Sage on macOS as a non-privileged user is a bad state of affairs. I played around with installing (compiling) homebrew as a normal user, this looks like it almost works but not quite there.  

Marc Culler

unread,
May 5, 2026, 7:13:44 PM (12 days ago) May 5
to sage-release
I was able to build Sage 10.9 on macOS (Intel and Arm) as a non-privileged user, without using Homebrew, and with many optional packages included.  The resulting Sage root was repackaged as the Sage_macOS app, which I just released and which is available from:

Of course this is not as easy as it once was.  The triumphal achievement of getting rid of the python spkg, which always worked fine for me, causes me to have to build python myself now.  And there are several other libraries that I now have to build myself as well, some of them being dependencies of python.

I have been considering assembling a binary package containing all of the "requirements" for building sage that could be unpacked in the sage/local directory and used to build Sage.  That would be like a half-way measure between a binary package and building from source.  If (any of) you are interested in that project, please get in touch with me.

- Marc

Dima Pasechnik

unread,
May 5, 2026, 10:33:17 PM (12 days ago) May 5
to sage-r...@googlegroups.com


On May 5, 2026 5:36:10 PM CDT, Volker Braun <vbrau...@gmail.com> wrote:
>I checked that there is no open blocker issue, and then made the release. I
>didn't read the details of all mailinglist threads.
>
>Sage doesn't build "out of the box" on OSX for some time now.
>
>There is the conda install which I guess works (haven't tried) but doesn't
>let you do local development.

Why do you think so?

Anyhow, Apple recently realised another major, and not really backwards compatible, upgrade to XCode, you have noticed it yourself. Perhaps you could have asked around whether more time is needed to polish things up?

>
>There is the system-wide (root-ful) homebrew which is tested on the CI,

>there is going to some combination of homebrew packages that lets you build
>the rest of Sage?

Yes, it's coming. If you paid attention, we now have taps for most non-Python standard packages.
A combination of the homebrew core,
<https://github.com/Macaulay2/homebrew-tap/tree/main/Formula>
and
<https://github.com/dimpase/homebrew-tap/tree/main/Formula>
is mostly complete.
Currently slightly stalled by a Meson regression (as far as building Sage goes, see <https://github.com/sagemath/sage/pull/41626> and <https://github.com/mesonbuild/meson/issues/15764>) - hopefully fixed very soon.


The only complicated non-python/pypi standard spkg which does not have a reasonable Homebrew install is GAP.
(GAP is something that can be built from source, but ideally we want everything installed from binary taps, like Macaulay2 does)

see
https://github.com/sagemath/sage/pull/40515
for the CI of this effort.

>
>On my Mac I need a pristine environment so I don't really want to install
>homebrew system-wide, and there I've still not managed to build Sage.

On arm64 Macs (you have one, right?)
Homebrew does not install anything outside /opt/homebrew (and, optionally, config dot-files in your user directory), so I don't really know what you mean by "pristine".

It's less intrusive than a typical macOS app.


>Granted I didn't have much time recently, it looks possible. But its
>definitely playing on hard mode.
>
>IMHO not being able to easily build Sage on macOS as a non-privileged user
>is a bad state of affairs.

Homebrew does not need more permissions for installing than XCode. Nowadays you can install Homebrew as a macOS package, from an Apple-blessed .pkg file, such as <https://github.com/Homebrew/brew/releases/download/5.1.9/Homebrew.pkg>, so I don't really understand "non-priviliged" standpoint here.

There is no Homebrew clone which uses only non-Apple tools, as far as I know.


> I played around with installing (compiling)
>homebrew as a normal user, this looks like it almost works but not quite
>there.

What is the point of this if you don't have XCode? Building everything using the vanilla clang doesn't seem like a viable install option.

Dima

John H Palmieri

unread,
May 5, 2026, 11:32:39 PM (12 days ago) May 5
to sage-release
On Tuesday, May 5, 2026 at 3:36:10 PM UTC-7 Volker Braun wrote:
I checked that there is no open blocker issue, and then made the release. I didn't read the details of all mailinglist threads.

I was hoping that you read the responses in this mailing list, for example the first response to the post about the release of 10.9.rc2, in which I reported that using --with-darwin-accelerate plus all of the recommended homebrew packages, Sage builds, but it does not build without --with-darwin-accelerate. To be honest, I didn't know if it was appropriate to mark an issue (as opposed to a PR) as a blocker, but I will do that now with https://github.com/sagemath/sage/issues/42096.
 

Sage doesn't build "out of the box" on OSX for some time now. 

There is the conda install which I guess works (haven't tried) but doesn't let you do local development.

There is the system-wide (root-ful) homebrew which is tested on the CI, there is going to some combination of homebrew packages that lets you build the rest of Sage? 

I do not use "sudo" when I install homebrew packages, although they are installed system-wide in /opt/.

Dima Pasechnik

unread,
May 6, 2026, 2:04:03 AM (12 days ago) May 6
to sage-r...@googlegroups.com
On May 5, 2026 5:36:10 PM CDT, Volker Braun <vbrau...@gmail.com> wrote:
>I checked that there is no open blocker issue, and then made the release. I
>didn't read the details of all mailinglist threads.
>
>Sage doesn't build "out of the box" on OSX for some time now.
>
>There is the conda install which I guess works (haven't tried) but doesn't
>let you do local development.

Why do you think so?

Anyhow, Apple recently realised another major, and not really
backwards compatible, upgrade to XCode, you have noticed it yourself.
Perhaps you could have asked around whether more time is needed to
polish things up?

>
>There is the system-wide (root-ful) homebrew which is tested on the CI,

>there is going to some combination of homebrew packages that lets you build
>the rest of Sage?

Yes, it's coming. If you paid attention, we now have taps for most
non-Python standard packages.
A combination of the homebrew core,
<https://github.com/Macaulay2/homebrew-tap/tree/main/Formula>
and
<https://github.com/dimpase/homebrew-tap/tree/main/Formula>
is mostly complete.
Currently slightly stalled by a Meson regression (as far as building
Sage goes, see <https://github.com/sagemath/sage/pull/41626> and
<https://github.com/mesonbuild/meson/issues/15764>) - hopefully fixed
very soon.


The only complicated non-python/pypi standard spkg which does not have
a reasonable Homebrew install is GAP.
(GAP is something that can be built from source, but ideally we want
everything installed from binary taps, like Macaulay2 does)

see
https://github.com/sagemath/sage/pull/40515
for the CI of this effort.

>
>On my Mac I need a pristine environment so I don't really want to install
>homebrew system-wide, and there I've still not managed to build Sage.

On arm64 Macs (you have one, right?)
Homebrew does not install anything outside /opt/homebrew (and,
optionally, config dot-files in your user directory), so I don't
really know what you mean by "pristine".

It's less intrusive than a typical macOS app.


>Granted I didn't have much time recently, it looks possible. But its
>definitely playing on hard mode.
>
>IMHO not being able to easily build Sage on macOS as a non-privileged user
>is a bad state of affairs.

Homebrew does not need more permissions for installing than XCode.
Nowadays you can install Homebrew as a macOS package, from an
Apple-blessed .pkg file, such as
<https://github.com/Homebrew/brew/releases/download/5.1.9/Homebrew.pkg>,
so I don't really understand "non-priviliged" standpoint here.

There is no Homebrew clone which uses only non-Apple tools, as far as I know.


> I played around with installing (compiling)
>homebrew as a normal user, this looks like it almost works but not quite
>there.

What is the point of this if you don't have XCode? Building everything
using the vanilla clang doesn't seem like a viable install option.

Best,
Dima

Eric Gourgoulhon

unread,
May 6, 2026, 8:23:35 AM (12 days ago) May 6
to sage-release
Thank you for the release, Volker!
Sage 10.9 fails to build on my Ubuntu 24.04 computer, both as an incremental build from Sage 10.9.beta8 (which built and ran OK) or as a full build from a fresh git clone;  this is due to the package rpy2_rinterface-3.6.6:

***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package:         rpy2_rinterface-3.6.6
  last build time: mai 6 13:38
  log file:        /home/eric/sage/10.9/logs/pkgs/rpy2_rinterface-3.6.6.log
  build directory: /home/eric/sage/10.9/local/var/tmp/sage/build/rpy2_rinterface-3.6.6

Here is what I did, after the fresh git clone: 

make configure
./configure --enable-download-from-upstream-url
MAKE="make -j16" make

Here are the files  config.log and rpy2_rinterface.log
I'm copying the content of the latter for convenience: 

Attempting to download package rpy2_rinterface-3.6.6.tar.gz from mirrors
https://github.com/sagemath/sage/releases/download/10.9/rpy2_rinterface-3.6.6.tar.gz
[......................................................................]
Setting up build directory /home/eric/sage/10.9/local/var/tmp/sage/build/rpy2_rinterface-3.6.6
No patch files found in ../patches
Host system: Linux tensor 6.8.0-110-generic #110-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 19 15:09:20 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
C compiler: gcc, Using built-in specs., COLLECT_GCC=gcc, COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper, OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa, OFFLOAD_TARGET_DEFAULT=1, Target: x86_64-linux-gnu, Configured with: ../src/configure -v --with-pkgversion='Ubuntu 13.3.0-6ubuntu2~24.04.1' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-13 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-13-EldibY/gcc-13-13.3.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-EldibY/gcc-13-13.3.0/debian/tmp-gcn/usr --enable-offload-defaulted --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=2, Thread model: posix, Supported LTO compression algorithms: zlib zstd, gcc version 13.3.0 (Ubuntu 13.3.0-6ubuntu2~24.04.1)
No stamp file for package 'rpy2_rinterface' in /home/eric/sage/10.9/local/var/lib/sage/installed
No spkg-legacy-uninstall script; nothing to do
[spkg-install] Installing rpy2_rinterface-3.6.6
[spkg-install] * Creating isolated environment: venv+pip...
[spkg-install] * Installing packages in isolated environment:
[spkg-install]   - cffi>=1.15.0
[spkg-install]   - packaging;platform_system=='Windows'
[spkg-install]   - setuptools >= 75;python_version=='3.8'
[spkg-install]   - setuptools >= 77;python_version>'3.8'
[spkg-install]   - wheel
[spkg-install] > /home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/bin/python3 -m pip
[spkg-install]   --python /tmp/build-env-_7leyfog/bin/python install --use-pep517 --no-warn-
[spkg-install]   script-location --no-compile -r /tmp/build-requirements-fztpkgbu.txt
[spkg-install] < Looking in links: /home/eric/sage/10.9/local/var/lib/sage/wheels
[spkg-install] < Ignoring packaging: markers 'platform_system == "Windows"' don't match your
[spkg-install]   environment
[spkg-install] < Ignoring setuptools: markers 'python_version == "3.8"' don't match your
[spkg-install]   environment
[spkg-install] < ERROR: Could not find a version that satisfies the requirement wheel (from
[spkg-install]   versions: none)
[spkg-install] < ERROR: No matching distribution found for wheel
[spkg-install]
[spkg-install] Traceback (most recent call last):
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/build/__main__.py", line 203, in _handle_build_error
[spkg-install]     yield
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/build/__main__.py", line 601, in main
[spkg-install]     built = build(
[spkg-install]             ^^^^^^
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/build/__main__.py", line 264, in build_package
[spkg-install]     out = _build(
[spkg-install]           ^^^^^^^
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/build/__main__.py", line 187, in _build
[spkg-install]     with _bootstrap_build_env(
[spkg-install]   File "/usr/lib/python3.12/contextlib.py", line 137, in __enter__
[spkg-install]     return next(self.gen)
[spkg-install]            ^^^^^^^^^^^^^^
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/build/__main__.py", line 153, in _bootstrap_build_env
[spkg-install]     install(builder.build_system_requires)
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/build/env.py", line 148, in install
[spkg-install]     self._env_backend.install_dependencies(requirements, constraints)
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/build/env.py", line 309, in install_dependencies
[spkg-install]     run_subprocess(cmd)
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/build/_ctx.py", line 71, in run_subprocess
[spkg-install]     subprocess.run(cmd, capture_output=True, check=True, cwd=cwd, env=env)
[spkg-install]   File "/usr/lib/python3.12/subprocess.py", line 571, in run
[spkg-install]     raise CalledProcessError(retcode, process.args,
[spkg-install] subprocess.CalledProcessError: Command '['/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/bin/python3', '-m', 'pip', '--python', '/tmp/build-env-_7leyfog/bin/python', 'install', '--use-pep517', '--no-warn-script-location', '--no-compile', '-r', '/tmp/build-requirements-fztpkgbu.txt']' returned non-zero exit status 1.
[spkg-install]
[spkg-install] ERROR Command '['/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/bin/python3', '-m', 'pip', '--python', '/tmp/build-env-_7leyfog/bin/python', 'install', '--use-pep517', '--no-warn-script-location', '--no-compile', '-r', '/tmp/build-requirements-fztpkgbu.txt']' returned non-zero exit status 1.
[spkg-install] Warning: building with "python3 -m build --wheel --outdir=dist   ." failed.
[spkg-install] Retrying with "python3 -m build --wheel --outdir=dist --no-isolation --skip-dependency-check  .".
[spkg-install] * Building wheel...
[spkg-install] /usr/bin/ld: cannot find -ltirpc: No such file or directory
[spkg-install] collect2: error: ld returned 1 exit status
[spkg-install] Traceback (most recent call last):
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/setuptools/_distutils/spawn.py", line 83, in spawn
[spkg-install]     subprocess.check_call(cmd, env=_inject_macos_ver(env))
[spkg-install]   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
[spkg-install]     raise CalledProcessError(retcode, cmd)
[spkg-install] subprocess.CalledProcessError: Command '['/usr/bin/gcc', '/tmp/tmp_pw_r_imyi8wgw/tmp/tmp_pw_r_imyi8wgw/test_pw_r.o', '-L/usr/lib/R/lib', '-lR', '-lpcre2-8', '-llzma', '-lbz2', '-lz', '-ltirpc', '-lrt', '-ldl', '-lm', '-licuuc', '-licui18n', '-o', '/tmp/tmp_pw_r_imyi8wgw/test_pw_r']' returned non-zero exit status 1.
[spkg-install]
[spkg-install] The above exception was the direct cause of the following exception:
[spkg-install]
[spkg-install] Traceback (most recent call last):
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/setuptools/_distutils/compilers/C/unix.py", line 307, in link
[spkg-install]     self.spawn(linker + ld_args)
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/setuptools/_distutils/compilers/C/base.py", line 1151, in spawn
[spkg-install]     spawn(cmd, **kwargs)
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/setuptools/_distutils/spawn.py", line 89, in spawn
[spkg-install]     raise DistutilsExecError(
[spkg-install] distutils.errors.DistutilsExecError: command '/usr/bin/gcc' failed with exit code 1
[spkg-install]
[spkg-install] During handling of the above exception, another exception occurred:
[spkg-install]
[spkg-install] Traceback (most recent call last):
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 389, in <module>
[spkg-install]     main()
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 373, in main
[spkg-install]     json_out["return_val"] = hook(**hook_input["kwargs"])
[spkg-install]                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 280, in build_wheel
[spkg-install]     return _build_backend().build_wheel(
[spkg-install]            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/setuptools/build_meta.py", line 438, in build_wheel
[spkg-install]     return _build(['bdist_wheel'])
[spkg-install]            ^^^^^^^^^^^^^^^^^^^^^^^
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/setuptools/build_meta.py", line 429, in _build
[spkg-install]     return self._build_with_temp_dir(
[spkg-install]            ^^^^^^^^^^^^^^^^^^^^^^^^^^
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/setuptools/build_meta.py", line 410, in _build_with_temp_dir
[spkg-install]     self.run_setup()
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/setuptools/build_meta.py", line 317, in run_setup
[spkg-install]     exec(code, locals())
[spkg-install]   File "<string>", line 165, in <module>
[spkg-install]   File "<string>", line 145, in get_r_c_extension_status
[spkg-install]   File "<string>", line 106, in get_c_extension_status
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/setuptools/_distutils/compilers/C/base.py", line 834, in link_executable
[spkg-install]     self.link(
[spkg-install]   File "/home/eric/sage/10.9/local/var/lib/sage/venv-python3.12/lib/python3.12/site-packages/setuptools/_distutils/compilers/C/unix.py", line 309, in link
[spkg-install]     raise LinkError(msg)
[spkg-install] distutils.compilers.C.errors.LinkError: command '/usr/bin/gcc' failed with exit code 1
[spkg-install]
[spkg-install] ERROR Backend subprocess exited when trying to invoke build_wheel
[spkg-install] ********************************************************************************
[spkg-install] Error building a wheel for rpy2_rinterface-3.6.6
[spkg-install] ********************************************************************************
************************************************************************
Error installing package rpy2_rinterface-3.6.6
************************************************************************
Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log files
  /home/eric/sage/10.9/logs/pkgs/rpy2_rinterface-3.6.6.log
and
  /home/eric/sage/10.9/config.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home/eric/sage/10.9/local/var/tmp/sage/build/rpy2_rinterface-3.6.6 and type 'make' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/home/eric/sage/10.9/local/var/tmp/sage/build/rpy2_rinterface-3.6.6' && '/home/eric/sage/10.9/sage' --buildsh)
When you are done debugging, you can type "exit" to leave the subshell.
************************************************************************

Thank you for your help. 

 Eric. 

Marc Culler

unread,
May 6, 2026, 8:37:08 AM (12 days ago) May 6
to sage-release
Your build log seems to be saying that you need to install libtirpc-dev.

- Marc

Dima Pasechnik

unread,
May 6, 2026, 10:41:33 AM (12 days ago) May 6
to sage-r...@googlegroups.com
This is https://github.com/sagemath/sage/issues/42121
> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/sage-release/71739d7d-c081-4914-99f0-f54d456497e0n%40googlegroups.com.

Eric Gourgoulhon

unread,
May 6, 2026, 10:43:01 AM (12 days ago) May 6
to sage-release
Le mercredi 6 mai 2026 à 14:37:08 UTC+2, marc....@gmail.com a écrit :
Your build log seems to be saying that you need to install libtirpc-dev.

- Marc

Thank you very much Marc, that was it!
After having installed the Ubuntu package libtripc-dev, the build was successful.

The requirement of libtripc-dev seems something new since Sage 10.9.beta8. It is not mentioned in the output of configure though (copy below).
I've added libtripc-dev to the list of prerequisites at

Thank you!

Eric. 

Output of ./configure: 
---------------------------------
real_configure:

    notice: the following SPKGs did not find equivalent system packages:

        brial cypari ecl eclib ecm fflas_ffpack fplll fpylll gap gc gengetopt givaro lcalc libbraiding libhomfly linbox lrcalc m4ri m4rie mathjax matplotlib maxima meson nauty pari pari_galdata pari_seadata_small patchelf planarity pplpy primecount primecountpy primesieve qhull singular   4ti2 _develop _recommended bliss coxeter3 fricas giac gp2c igraph libgraphviz libnauty libsemigroups msolve onetbb pari_elldata pari_galpol pari_nftables pari_seadata polymake sbcl sirocco texlive_luatex xindy
       
checking for the package system in use... debian
real_configure:

    hint: installing the following system packages, if not
    already present, is recommended and may avoid having to
    build them (though some may have to be built anyway):

      $ sudo apt-get update
      $ sudo apt-get install libbrial-dev libbrial-groebner-dev ecl libec-dev eclib-tools gmp-ecm libecm-dev fflas-ffpack libfplll-dev gap libgap-dev libgc-dev gengetopt libgivaro-dev lcalc liblfunction-dev libbraiding-dev libhomfly-dev liblinbox-dev liblrcalc-dev libm4ri-dev libm4rie-dev maxima-sage maxima meson nauty pari-gp2c libpari-dev pari-doc pari-elldata pari-galdata pari-galpol pari-seadata patchelf libplanarity-dev planarity libprimecount-dev primecount libprimesieve-dev qhull-bin libqhull-dev singular singular-doc libsingular4-dev

real_configure:

    hint: installing the following system packages, if not
    already present, may provide additional optional features:

      $ sudo apt-get update
      $ sudo apt-get install 4ti2 gpgconf openssh-client default-jdk libavdevice-dev fricas libgiac-dev xcas pari-gp2c libigraph-dev libgraphviz-dev libnauty-dev libtbb-dev polymake libpolymake-dev sbcl texlive-luatex xindy

real_configure:

    hint: After installation, re-run configure using:

      $ make reconfigure

Eric Gourgoulhon

unread,
May 6, 2026, 10:47:38 AM (12 days ago) May 6
to sage-release
PS: Dima, I've replied before seeing your message. Thanks for it!

Henri Girard

unread,
May 6, 2026, 12:40:01 PM (12 days ago) May 6
to sage-r...@googlegroups.com

I use ubuntu 26 dev and sage compiled without any problems I use sage git too

--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.

Volker Braun

unread,
May 6, 2026, 2:41:45 PM (12 days ago) May 6
to sage-release
On Wednesday, May 6, 2026 at 8:04:03 AM UTC+2 Dima Pasechnik wrote:
Anyhow, Apple recently realised another major, and not really
backwards compatible, upgrade to XCode, you have noticed it yourself.

Well XCode updates are always broken, thats just on par for the course. I should have said: the CI checks that some version of XCode lets you build with some version of homebrew packages.
 
Perhaps you could have asked around whether more time is needed to
polish things up?

It's [i.e. homebrew] less intrusive than a typical macOS app.

Thats not true, macOS applications (.app's) are quite well-contained (software deployment still sucks because there is no official package management, but thats another story...)

What deserves a special circle in hell are packages (.pkg files) which are just a double-clickable landmine that then spews files into random locations. Basically windows 3.11 executable installers for macOS.

In any case, we can just make another release when we want. Let me know when you are happy with macOS support and I can make a release, no big deal.


Dima Pasechnik

unread,
May 7, 2026, 3:30:18 PM (11 days ago) May 7
to sage-r...@googlegroups.com
On Wed, May 6, 2026 at 1:41 PM Volker Braun <vbrau...@gmail.com> wrote:
>
> On Wednesday, May 6, 2026 at 8:04:03 AM UTC+2 Dima Pasechnik wrote:
>
> Anyhow, Apple recently realised another major, and not really
> backwards compatible, upgrade to XCode, you have noticed it yourself.
>
>
> Well XCode updates are always broken, thats just on par for the course. I should have said: the CI checks that some version of XCode lets you build with some version of homebrew packages.
>
>
> Perhaps you could have asked around whether more time is needed to
> polish things up?
>
>
> It's [i.e. homebrew] less intrusive than a typical macOS app.
>
>
> Thats not true, macOS applications (.app's) are quite well-contained (software deployment still sucks because there is no official package management, but thats another story...)
>
> What deserves a special circle in hell are packages (.pkg files) which are just a double-clickable landmine that then spews files into random locations. Basically windows 3.11 executable installers for macOS.

.pkg files are signed. .app files are also notarized (scanned by some
apple tools and stamped, for $100 a year or so), so what.
Python distributes macOS Python as .pkg, too.
It's all question of trust. Do we trust Apple? Do we trust Python.org?
Do we trust brew.sh (Homebrew)? Do we trust PyPI?
I don't think I trust Apple more than I trust Python.org or Homebrew.
Apple is good in security theater, that's all.

>
> In any case, we can just make another release when we want. Let me know when you are happy with macOS support and I can make a release, no big deal.

OK, let's fix all the outstanding issues with Sage building on major
distros, and the corresponding docs,
conda lock files, uv lock files are synched, etc.
then make 10.9.1 or so, say by the end of the month?

In the future, can we please have a code freeze period, announced in
advance, say, 2 weeks in advance,
so that the loose ends are tied up, testing of installation procedures
is done, and no other activity on develop is happening?

IMHO it's for the release manager to manage people involved in the
release, too, the release manager doesn't have to suffer in silence,
with the only means of communications being beta and rc numbering :-)

Dima

Dima Pasechnik

unread,
May 7, 2026, 4:15:03 PM (11 days ago) May 7
to sage-r...@googlegroups.com
On Tue, May 5, 2026 at 6:13 PM Marc Culler <marc....@gmail.com> wrote:
>
> I was able to build Sage 10.9 on macOS (Intel and Arm) as a non-privileged user, without using Homebrew, and with many optional packages included. The resulting Sage root was repackaged as the Sage_macOS app, which I just released and which is available from:
> https://github.com/3-manifolds/Sage_macOS/releases.
>
> Of course this is not as easy as it once was. The triumphal achievement of getting rid of the python spkg, which always worked fine for me, causes me to have to build python myself now. And there are several other libraries that I now have to build myself as well, some of them being dependencies of python.

What worked fine for you created extra workload, as well as pure time
waste, for many other people, unfortunately.

>
> I have been considering assembling a binary package containing all of the "requirements" for building sage that could be unpacked in the sage/local directory and used to build Sage. That would be like a half-way measure between a binary package and building from source. If (any of) you are interested in that project, please get in touch with me.

I'd rather propose concentrating on creating the needed missing
Homebrew formulae, so that the non-python packages needed to build
Sage (sagelib, to be precise) are all here.
We are actually almost there, see
https://github.com/Macaulay2/homebrew-tap/,
https://github.com/dimpase/homebrew-tap/,
https://github.com/gap-system/homebrew-gap/.

We don't want yet another version of sage-distro with all of its
problems, such as lack of proper package dependency management, etc.

Dima

>
> - Marc
> On Tuesday, May 5, 2026 at 5:36:10 PM UTC-5 Volker Braun wrote:
>>
>> I checked that there is no open blocker issue, and then made the release. I didn't read the details of all mailinglist threads.
>>
>> Sage doesn't build "out of the box" on OSX for some time now.
>>
>> There is the conda install which I guess works (haven't tried) but doesn't let you do local development.
>>
>> There is the system-wide (root-ful) homebrew which is tested on the CI, there is going to some combination of homebrew packages that lets you build the rest of Sage?
>>
>> On my Mac I need a pristine environment so I don't really want to install homebrew system-wide, and there I've still not managed to build Sage. Granted I didn't have much time recently, it looks possible. But its definitely playing on hard mode.
>>
>> IMHO not being able to easily build Sage on macOS as a non-privileged user is a bad state of affairs. I played around with installing (compiling) homebrew as a normal user, this looks like it almost works but not quite there.
>> On Tuesday, May 5, 2026 at 7:05:28 PM UTC+2 John H Palmieri wrote:
>>>
>>> I'm curious: why release 10.9 when it doesn't build out of the box on OS X?
>>>
>>>
>>> On Monday, May 4, 2026 at 3:45:36 PM UTC-7 Volker Braun wrote:
>>>>
>>>> The "master" git branch has been updated to Sage-10.9. As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html
>>>>
>>>> There was no change over 10.9.rc2
>>>>
>>>>
> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/sage-release/4ffaf495-761a-4d81-8007-6cc7d6bb06d3n%40googlegroups.com.

Volker Braun

unread,
May 7, 2026, 6:19:33 PM (10 days ago) May 7
to sage-release
On Thursday, May 7, 2026 at 9:30:18 PM UTC+2 Dima Pasechnik wrote:
In the future, can we please have a code freeze period, announced in
advance, say, 2 weeks in advance,
so that the loose ends are tied up, testing of installation procedures
is done, and no other activity on develop is happening?

Like how about I release rc0 on, say, April 19 and then wait until May 5 to make the release? That`s even more than two weeks. That did happen ;)


Dima Pasechnik

unread,
May 9, 2026, 8:27:57 PM (8 days ago) May 9
to sage-r...@googlegroups.com
How about setting up a checklist for the releases, so that everything builds on the major platforms, documentation is up to date,etc.

Say, one opens an issue with this checklist (once rc0 is out?), and the release doesn't happen until everything is ticked off?

Dima

Tobias Diez

unread,
May 11, 2026, 4:11:35 AM (7 days ago) May 11
to sage-release
I'd say this is a great idea. In addition, we could also use Github's milestones to collect issues that should be fixed in the current release cycle - personally, I find this more transparent than the current handling via the "blocker" label. 

Perhaps these ideas should be discussed and then voted on on the main mailing list?
Reply all
Reply to author
Forward
0 new messages