Sage 10.8.rc2 released

37 views
Skip to first unread message

Volker Braun

unread,
Dec 11, 2025, 6:45:49 PM (3 days ago) Dec 11
to sage-release
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


aa8778f4063 (tag: 10.8.rc2, github/develop) Updated SageMath version to 10.8.rc2
7202dcde7d6 gh-41279: build givaro, fflas-ffpack and linbox without native arch in SAGE_FAT_BINARY
89e60a80088 gh-41260: Fix --with-python option not being honored when cache exists
0fc8ed5144a (tag: 10.8.rc1) Updated SageMath version to 10.8.rc1

Marc Culler

unread,
Dec 12, 2025, 1:35:07 PM (3 days ago) Dec 12
to sage-release
I am unable to build cypari2 with 10.8rc2 on macOS.  According to the log file the problem is:

[spkg-install] ../meson.build:65:10: ERROR: C shared or static library 'pari' not found

But it **should** be found, because I have already installed pari in sage/local with Sage's pari spkg.
% ls sage/local/lib/libpari*
sage/local/lib/libpari-gmp-tls.dylib sage/local/lib/libpari.dylib
% ls sage/local/include | grep pari
pari

Looking at the meson.build file, it seems that it does not check for pari in sage/local/lib.  It only checks for a homebrew pari.  It should be possible to build cypari2 with a pari installed in sage/local.  That should be the case even if Sage decides to get rid of the pari spkg (which would be unwise, but expected).  It should be the case for all library dependencies (including Python3) that if those libraries are already installed in sage/local then packages which need them will look for them there.

- Marc

Dima Pasechnik

unread,
Dec 12, 2025, 4:48:25 PM (3 days ago) Dec 12
to sage-r...@googlegroups.com
On Fri, Dec 12, 2025 at 12:35 PM Marc Culler <marc....@gmail.com> wrote:
>
> I am unable to build cypari2 with 10.8rc2 on macOS. According to the log file the problem is:
>
> [spkg-install] ../meson.build:65:10: ERROR: C shared or static library 'pari' not found
>
> But it **should** be found, because I have already installed pari in sage/local with Sage's pari spkg.
> % ls sage/local/lib/libpari*
> sage/local/lib/libpari-gmp-tls.dylib sage/local/lib/libpari.dylib
> % ls sage/local/include | grep pari
> pari
>
> Looking at the meson.build file, it seems that it does not check for pari in sage/local/lib. It only checks for a homebrew pari. It should be possible to build cypari2 with a pari installed in sage/local. That should be the case even if Sage decides to get rid of the pari spkg (which would be unwise, but expected). It should be the case for all library dependencies (including Python3) that if those libraries are already installed in sage/local then packages which need them will look for them there.

It's a cypari2 bug, not only a sage bug, no? cypari2 should have an
option to specify a custom location for pari-gp, and
sage should pass this location to cypari2 install script, via
variables SAGE_PARI_CFG and
SAGE_PARI_PREFIX, or even via
SAGE_CONFIGURE_PARI="--with-pari=$SAGE_PARI_PREFIX" set in
build/bin/sage-build-env

>
> - Marc
>
> On Thursday, December 11, 2025 at 5:45:49 PM UTC-6 Volker Braun wrote:
>>
>> 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
>>
>>
>> aa8778f4063 (tag: 10.8.rc2, github/develop) Updated SageMath version to 10.8.rc2
>> 7202dcde7d6 gh-41279: build givaro, fflas-ffpack and linbox without native arch in SAGE_FAT_BINARY
>> 89e60a80088 gh-41260: Fix --with-python option not being honored when cache exists
>> 0fc8ed5144a (tag: 10.8.rc1) Updated SageMath version to 10.8.rc1
>
> --
> 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/0655f2f6-f7c3-4fb4-8237-d8ea8d1ffc7bn%40googlegroups.com.

Marc Culler

unread,
Dec 12, 2025, 5:23:07 PM (3 days ago) Dec 12
to sage-release
On Friday, December 12, 2025 at 3:48:25 PM UTC-6 Dima Pasechnik wrote:
It's a cypari2 bug, not only a sage bug, no? cypari2 should have an
option to specify a custom location for pari-gp, and
sage should pass this location to cypari2 install script, via
variables SAGE_PARI_CFG and
SAGE_PARI_PREFIX, or even via
SAGE_CONFIGURE_PARI="--with-pari=$SAGE_PARI_PREFIX" set in
build/bin/sage-build-env

Yes, that would be a good idea.

- Marc
 
Reply all
Reply to author
Forward
0 new messages