On Saturday, September 23, 2023 at 10:07:24 PM UTC-4 John H Palmieri wrote:
Building Sage's own gfortran worked to build scipy (and this is an argument
to keep the gfortran package around, by the way).
I just successfully upgraded Sage only by doing this as well. The homebrew
scipy is a
After an upgrade of macOS and Xcode CLT, I also see this problem on my
system.
There is an open issue https://github.com/mesonbuild/meson/issues/12282 for
this.
On Thursday, September 21, 2023 at 4:52:56 PM UTC-7 John H Palmieri wrote:
> A new problem, after upgrading to OS X 13.6 and the
On Sun, Sep 24, 2023 at 5:53 PM John H Palmieri wrote:
>
> I've already tried uninstalling and reinstalling every homebrew package, and
> it didn't help.
I meant removing the whole /opt/homebrew/ and reinstalling homebrew
from scratch.
> I've also been doing "make distclean" and "./configure"
I've already tried uninstalling and reinstalling every homebrew package,
and it didn't help. I've also been doing "make distclean" and "./configure"
in between attempts.
I'm confused about your comment about meson_python: I don't think that Sage
ordinarily uses a system package of this
both meson and meson_python may potentially come from the system (homebrew
in your case).
Make sure they are up to date, and you don't have these packages installed
in Sage.
And run ./configure
Perhaps the whole homebrew must be reinstated after an OS update, too.
On Sun, 24 Sept 2023, 03:07
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
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
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
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
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:
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
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
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
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
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 the cached download file for homebrew's gcc
and tried again, same result. I have not yet tried Sage's gcc.
On
Where is gfortran coming from here?
Do you build it with Sage, or use an external one?
If the external one, e.g. from Homebrew, you most probably need to
update/reinstall.
Ditto in Sage
On Fri, 22 Sept 2023, 00:52 John H Palmieri, wrote:
> A new problem, after upgrading to OS X 13.6 and the
By the way, it also says
A full log can be found at
/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/var/lib/sage/venv-python3.11/var/tmp/sage/build/scipy-1.11.2/src/.mesonpy-sxi6gtt6/build/meson-logs/meson-log.txt
but there is no such file, indeed no such directory ".mesonpy-".
A new problem, after upgrading to OS X 13.6 and the newest version of the
command-line tools: scipy fails to build again, this time with the error:
../../meson.build:82:0: ERROR: Unable to detect linker for compiler
`gfortran -Wl,--version
On Mon, 18 Sept 2023 at 09:50, Dima Pasechnik wrote:
> run
>
> make pytest
>
> (or ./sage -i pytest)
>
> to install it and have it ready for Sage.
> (i.e. install it into Sage's venv)
>
Thanks Dima
John
>
> On Mon, Sep 18, 2023 at 9:04 AM John Cremona
> wrote:
> >
> > What should I do to
run
make pytest
(or ./sage -i pytest)
to install it and have it ready for Sage.
(i.e. install it into Sage's venv)
On Mon, Sep 18, 2023 at 9:04 AM John Cremona wrote:
>
> What should I do to avoid this message when running "make testlong":
>
> pytest is not installed in the venv, skip
What should I do to avoid this message when running "make testlong":
pytest is not installed in the venv, skip checking tests that rely on it
i.e. how should I install pytest. System-wide or what?
John
On Mon, 18 Sept 2023 at 01:08, Matthias Köppe
wrote:
> I've pushed a fix to
I've pushed a fix to https://github.com/sagemath/sage/pull/36276
On Sunday, September 17, 2023 at 5:02:05 PM UTC-7 Matthias Köppe wrote:
> Yes, it's a bug in the build system. Running CONFIG_SHELL="bash -x"
> ./configure
>
> + printf '%s\n' 'configure:49868: result: no; skipping check'
>
Yes, it's a bug in the build system. Running CONFIG_SHELL="bash -x"
./configure
+ printf '%s\n' 'configure:49868: result: no; skipping check'
+ printf '%s\n' 'no; skipping check'
+ sage_spkg_install_meson-python=yes
./configure: line 49870: sage_spkg_install_meson-python=yes: command not
On Sun, Sep 17, 2023 at 7:25 PM John H Palmieri
wrote:
>
> Similar problem for me on OS X. I don't understand something: the
dependencies for scipy include meson_python, but that package is not
installed before scipy attempts to build, and fails. Running "make
meson_python" and then "make scipy"
Similar problem for me on OS X. I don't understand something: the
dependencies for scipy include meson_python, but that package is not
installed before scipy attempts to build, and fails. Running "make
meson_python" and then "make scipy" succeeds, as does "make".
On Saturday, September 16,
FWW, on Debian testing running on core i7 + 16 GB RAM, upgrading 10.2.beta2
to 10.2.beta3 went smoothly (without having to mess with meson) ; ptestlong
gives two permanent failures :
-- sage
-t --long --warn-long 217.3
Succeeded after sage -pip install meson-python.
On Sunday, September 17, 2023 at 6:52:59 AM UTC+9 Kwankyu Lee wrote:
> Incremental build failed
>
> [scipy-1.11.2]
> [..]
> [scipy-1.11.2] scipy-1.11.2
> [scipy-1.11.2]
Incremental build failed
[scipy-1.11.2]
[..]
[scipy-1.11.2] scipy-1.11.2
[scipy-1.11.2]
[sagelib-10.2.beta3] Removing file or directory
28 matches
Mail list logo
