[sage-release] Re: Sage 10.3.rc0 released

2024-02-28 Thread Matthias Köppe
I have a workaround for the pillow/openjpeg problem in https://github.com/sagemath/sage/pull/37505 On Wednesday, February 28, 2024 at 5:47:04 PM UTC-8 Matthias Köppe wrote: > Can confirm also on macOS x86_64 with just upgraded openjpeg. > And upgrading to pillow-10.2.0 (latest) does NOT help.

[sage-release] Re: Sage 10.3.rc0 released

2024-02-28 Thread Matthias Köppe
Can confirm also on macOS x86_64 with just upgraded openjpeg. And upgrading to pillow-10.2.0 (latest) does NOT help. On Wednesday, February 28, 2024 at 2:22:08 PM UTC-8 John H Palmieri wrote: > The failing command: > > gcc -fno-strict-overflow -Wsign-compare -Wunreachable-code -fno-common >

[sage-release] Re: Sage 10.3.rc0 released

2024-02-28 Thread John H Palmieri
The failing command: gcc -fno-strict-overflow -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -O3 -Wall -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk -g -O2 -g -DHAVE_LIBTIFF -DHAVE_LIBJPEG -DHAVE_OPENJPEG -DHAVE_LIBZ -DHAVE_XCB -DPILLOW_VERSION=\"10.1.0\"

[sage-release] Re: Sage 10.3.rc0 released

2024-02-28 Thread John H Palmieri
OS X, Apple Silicon, with many homebrew packages, including a recently upgraded openjpeg (from 2.5.0 to 2.5.1): pillow is failing to build, with the error message src/libImaging/Jpeg2KDecode.c:673:43: error: too few arguments to function call, expected 3, have 2

Re: [sage-release] Re: Sage 10.3.rc0 released

2024-02-28 Thread Jaap Spies
Goedemiddag, >From the logs/tests.log: see attachment. Jaap On Tue, Feb 27, 2024 at 1:01 PM Dima Pasechnik wrote: > Goedemiddag Jaap, > > would you be so kind to look at logs/tests.log and see where exactly the > crash occurs (lines before the crash are printed, so it can be put down to > the

Re: [sage-release] Re: Sage 10.3.rc0 released

2024-02-27 Thread Dima Pasechnik
Goedemiddag Jaap, would you be so kind to look at logs/tests.log and see where exactly the crash occurs (lines before the crash are printed, so it can be put down to the exact place it). And post the relevant lines of logs/tests.log here. Dima On Tue, Feb 27, 2024 at 11:02 AM Jaap Spies

Re: [sage-release] Re: Sage 10.3.rc0 released

2024-02-27 Thread Jaap Spies
Operating System: Fedora Linux 39 Kernel Version: 6.7.3-200.fc39.x86_64 (64-bit) Processors: 24 × 13th Gen Intel® Core™ i7-13700KF Memory: 31,2 GiB of RAM Same persistent error: Unhandled SIGSEGV: A segmentation fault occurred. This probably occurred because a *compiled* module has a bug in it

[sage-release] Re: Sage 10.3.rc0 released

2024-02-26 Thread Emmanuel Charpentier
Thanks a lot ! I'll have to ((re-)^n)read the Developer's Guide and the Installation Guide... Le lundi 26 février 2024 à 21:44:27 UTC+1, matthia...@gmail.com a écrit : On Monday, February 26, 2024 at 12:26:04 PM UTC-8 emanuel.c...@gmail.com wrote: Question : how to modify Sage’s configuration

[sage-release] Re: Sage 10.3.rc0 released

2024-02-26 Thread Matthias Köppe
On Monday, February 26, 2024 at 12:26:04 PM UTC-8 emanuel.c...@gmail.com wrote: Question : how to modify Sage’s configuration (as used by make reconfigure) without having to re-state *all* the configuration ? eval ./configure $(./config.status --config) --without-system-brial -- You received

[sage-release] Re: Sage 10.3.rc0 released

2024-02-26 Thread Emmanuel Charpentier
On Debian testing running on core i7 + 16 GB RAM, upgrading 10.3.beta8 to 10.3.rc0 initially failed ; deleting and rebuilding the documentation succeeded. Running ptestlong initially raised the seven polybori-related failures already reported