Re: [sage-release] Re: Sage 10.2.beta3 released

2023-09-23 Thread John H Palmieri
This is with an Apple Silicon laptop, M2 chip, in case that matters. On Saturday, September 23, 2023 at 10:06:36 AM UTC-7 John H Palmieri wrote: > I tried the venv approach in the scipy docs, and I ran into the same error. > > On Saturday, September 23, 2023 at 1:31:34 AM UTC-7 Dima Pasechnik

Re: [sage-release] Re: Sage 10.2.beta3 released

2023-09-23 Thread John H Palmieri
Same result if I do `pip3 install scipy --no-binary scipy` (another of their suggested ways of building from source). I guess something is broken with my fortran compiler, but I don't know how to troubleshoot it. On Saturday, September 23, 2023 at 2:35:52 PM UTC-7 John H Palmieri wrote: > It

Re: [sage-release] Re: Sage 10.2.beta3 released

2023-09-23 Thread Dima Pasechnik
As far as I can gather from scipy bug tracker, they can build on M2 just fine https://github.com/scipy/scipy/issues/18308 On Sat, 23 Sept 2023, 18:07 John H Palmieri, wrote: > This is with an Apple Silicon laptop, M2 chip, in case that matters. > > On Saturday, September 23, 2023 at 10:06:36 

Re: [sage-release] Re: Sage 10.2.beta3 released

2023-09-23 Thread John H Palmieri
If by "they" you mean scipy, then: I have no problems building scipy on another OS X machine: an Intel machine running OS X 13.5.2 (rather than 13.6). "xcode-select --version" reports the same for both machines, but I don't know how informative this is. "gfortran --version" says GNU Fortran

Re: [sage-release] Re: Sage 10.2.beta3 released

2023-09-23 Thread John H Palmieri
I tried the venv approach in the scipy docs, and I ran into the same error. On Saturday, September 23, 2023 at 1:31:34 AM UTC-7 Dima Pasechnik wrote: > Can you build scipy from source using their instructions? > > On Sat, 23 Sept 2023, 06:25 John H Palmieri, wrote: > >> It's from homebrew's

Re: [sage-release] Re: Sage 10.2.beta3 released

2023-09-23 Thread Dima Pasechnik
do they even support gcc/gfortran 13? On Sat, 23 Sept 2023, 23:04 John H Palmieri, wrote: > Same result if I do `pip3 install scipy --no-binary scipy` (another of > their suggested ways of building from source). I guess something is broken > with my fortran compiler, but I don't know how to

Re: [sage-release] Re: Sage 10.2.beta3 released

2023-09-23 Thread John H Palmieri
It didn't work for me. At least directly attempting a scipy build left an intact log file. Any clues about what's broken on this machine? Build started at 2023-09-23T14:31:26.723020 Main binary: /Users/palmieri/Downloads/scipy-1.11.2/venv/bin/python3 Build Options:

Re: [sage-release] Re: Sage 10.2.beta3 released

2023-09-23 Thread John H Palmieri
Building Sage's own gfortran worked to build scipy (and this is an argument to keep the gfortran package around, by the way). Alternatively, building all of scipy's dependencies and then using `./sage --python3 -m pip install scipy` also seems to have worked. I then "touch"ed the appropriate

Re: [sage-release] Re: Sage 10.2.beta3 released

2023-09-23 Thread Dima Pasechnik
Can you build scipy from source using their instructions? On Sat, 23 Sept 2023, 06:25 John H Palmieri, wrote: > It's from homebrew's gcc. I did `brew reinstall gcc` followed by `make > distclean && ./configure && make meson_python && make` and it still fails > at scipy, same error. I removed