Another problem building Sage on 25.04

[Richard Quint]

I am unable to build sage-10.6 from source on a PC running Ubuntu
25.04.  I was able to build successfully from the same source file,
sage-10.6.tar.gz, on the same machine when it was running Ubuntu 24.10. 
After upgrading to 25.04 and ensuring all updates were installed, I
deleted my existing SAGE_ROOT, ~/Sage/sage-10.6, extracted sage-10.6
from the source file as ~/Sage/sage-10.6 (as before), opened a terminal
in ~/Sage/sage-10.6 and ran ./configure followed by make.  I got

    Error building Sage.

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

    * package:         sagelib-10.6

As instructed in the log files, attached are ~/Sage/sage-10.6/config.log
and ~/Sage/sage-10.6/logs/pkgs/sagelib-10.6.log

I checked for the installation status of Python's setuptools and the
version of Python
    rquint@Iphegenia:~$ apt list --installed | grep setuptools

    WARNING: apt does not have a stable CLI interface. Use with caution
in scripts.

    python3-setuptools-whl/plucky,plucky,now 75.8.0-1 all
[installed,automatic]
    python3-setuptools/plucky,plucky,now 75.8.0-1 all [installed]
    rquint@Iphegenia:~$ python --version
    Python 3.13.3

[Antonio Rojas]

Ubuntu 25.04 is shipping a broken version of m4ri, use the bundled version.

[Dima Pasechnik]

As your gcc is now gcc-15, supporting it is work in progress.

Hopefully complete by the time Sage 10.7 is out. (there are many fixes merged in the current beta, but not all, still)

--
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 sage-devel+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sage-devel/95d5012a-b405-4b6c-a7ae-d40c1dbdebc3%40gmail.com.

[Richard Quint]

On 5/23/25 3:43 PM, Antonio Rojas wrote:
> Ubuntu 25.04 is shipping a broken version of m4ri, use the bundled
> version.

Following Antonio's suggestion I tried a clean install with

./configure --with-system-m4ri=no

 and everything worked perfectly.