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

[kcrisman]

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 newer version, fwiw.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/6770e52d-1e1c-483d-8c1b-faae64854129n%40googlegroups.com.

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

[Dima Pasechnik]

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" 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 (except on gentoo?), so it always 
> builds its own. It is using the homebrew installation of meson. I do not have 
> the homebrew meson-python package.

It is (or going to) be available with ./configure --enable-system-site-packages
(after https://github.com/sagemath/sage/pull/36256 and
https://github.com/sagemath/sage/pull/36276)

>
> On Sunday, September 24, 2023 at 3:28:22 AM UTC-7 Dima Pasechnik wrote:
>>
>> 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 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).
>>>
>>> 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 file to convince Sage that scipy had built, and the rest of 
>>> the build succeeded, except for some extra warnings during doctests: "ld: 
>>> warning: duplicate -rpath [...SAGE_ROOT/local/lib...] ignored"
>>>
>>> On Saturday, September 23, 2023 at 3:59:40 PM UTC-7 John H Palmieri wrote:

 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 (Homebrew GCC 13.2.0) 13.2.0
 Copyright (C) 2023 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

 and this is the one that scipy finds. On the M2 machine, Sage's scipy 
 built back in August with earlier versions of the OS (probably 13.5.2) and 
 command-line tools and gfortran (13.1.0).


 On Saturday, September 23, 2023 at 3:34:29 PM UTC-7 Dima Pasechnik wrote:
>
> 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 troubleshoot it.
>>
>> On Saturday, September 23, 2023 at 2:35:52 PM UTC-7 John H Palmieri 
>> wrote:
>>>
>>> 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: 
>>> -Dprefix=/Users/palmieri/Downloads/scipy-1.11.2/build-install
>>> Python system: Darwin
>>> The Meson build system
>>> Version: 1.2.1
>>> Source dir: /Users/palmieri/Downloads/scipy-1.11.2
>>> Build dir: /Users/palmieri/Downloads/scipy-1.11.2/build
>>> Build type: native build
>>> Project name: SciPy
>>> Project version: 1.11.2
>>> ---
>>> Detecting compiler via: `cc --version` -> 0
>>> stdout:
>>> Apple clang version 15.0.0 (clang-1500.0.40.1)
>>> Target: arm64-apple-darwin22.6.0
>>> Thread model: posix
>>> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
>>> ---
>>> Running command: cc -E -dM -
>>> -
>>> ---
>>> Detecting linker via: `cc -Wl,--version` -> 1
>>> stderr:
>>> ld: unknown options: --version
>>> clang: error: linker command failed with exit code 1 (use -v to see 
>>> invocation)
>>> ---
>>> ---
>>> Detecting Apple linker via: `cc -Wl,-v` -> 1
>>> stderr:
>>> @(#)PROGRAM:ld  PROJECT:dyld-1015.7
>>> BUILD 18:48:48 Aug 22 2023
>>> configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 
>>> i386 x86_64 x86_64h armv6m armv7k armv7m armv7em
>>> will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m armv7k 
>>> armv7m armv7em
>>> LTO support using: LLVM version 15.0.0 (static support for 29, runtime 
>>> is 29)
>>> TAPI support using: Apple TAPI version 15.0.0 

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

[John H Palmieri]

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 (except on gentoo?), so it always 
builds its own. It is using the homebrew installation of meson. I do not 
have the homebrew meson-python package.

On Sunday, September 24, 2023 at 3:28:22 AM UTC-7 Dima Pasechnik wrote:

> 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 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).
>>
>> 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 file to convince Sage that scipy had built, and 
>> the rest of the build succeeded, except for some extra warnings during 
>> doctests: "ld: warning: duplicate -rpath [...SAGE_ROOT/local/lib...] 
>> ignored"
>>
>> On Saturday, September 23, 2023 at 3:59:40 PM UTC-7 John H Palmieri wrote:
>>
>>> 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 (Homebrew GCC 13.2.0) 13.2.0
>>> Copyright (C) 2023 Free Software Foundation, Inc.
>>> This is free software; see the source for copying conditions.  There is 
>>> NO
>>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
>>> PURPOSE.
>>>
>>> and this is the one that scipy finds. On the M2 machine, Sage's scipy 
>>> built back in August with earlier versions of the OS (probably 13.5.2) and 
>>> command-line tools and gfortran (13.1.0).
>>>
>>>
>>> On Saturday, September 23, 2023 at 3:34:29 PM UTC-7 Dima Pasechnik wrote:
>>>
 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 troubleshoot it.
>
> On Saturday, September 23, 2023 at 2:35:52 PM UTC-7 John H Palmieri 
> wrote:
>
>> 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: 
>> -Dprefix=/Users/palmieri/Downloads/scipy-1.11.2/build-install
>> Python system: Darwin
>> The Meson build system
>> Version: 1.2.1
>> Source dir: /Users/palmieri/Downloads/scipy-1.11.2
>> Build dir: /Users/palmieri/Downloads/scipy-1.11.2/build
>> Build type: native build
>> Project name: SciPy
>> Project version: 1.11.2
>> ---
>> Detecting compiler via: `cc --version` -> 0
>> stdout:
>> Apple clang version 15.0.0 (clang-1500.0.40.1)
>> Target: arm64-apple-darwin22.6.0
>> Thread model: posix
>> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
>> ---
>> Running command: cc -E -dM -
>> -
>> ---
>> Detecting linker via: `cc -Wl,--version` -> 1
>> stderr:
>> ld: unknown options: --version 
>> clang: error: linker command failed with exit code 1 (use -v to see 
>> invocation)
>> ---
>> ---
>> Detecting Apple linker via: `cc -Wl,-v` -> 1
>> stderr:
>> @(#)PROGRAM:ld  PROJECT:dyld-1015.7
>> BUILD 18:48:48 Aug 22 2023
>> configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 
>> i386 x86_64 x86_64h armv6m armv7k armv7m armv7em
>> will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m 
>> armv7k armv7m armv7em
>> LTO support using: LLVM version 15.0.0 (static support for 29, 
>> runtime is 29)
>> TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3)
>> Library search paths:
>> /opt/homebrew/opt/primesieve/lib
>> /opt/homebrew/opt/bdw-gc/lib
>> /opt/homebrew/opt/libpng/lib
>> /opt/homebrew/opt/ntl/lib
>> /opt/homebrew/opt/bzip2/lib
>> /opt/homebrew/opt/readline/lib
>> /opt/homebrew/lib
>> /usr/local/lib
>> Framework search paths:
>> ld: Undefined symbols:
>>   _main, referenced from:
>> 

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

[Dima Pasechnik]

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 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).
>
> 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 file to convince Sage that scipy had built, and the rest of
> the build succeeded, except for some extra warnings during doctests: "ld:
> warning: duplicate -rpath [...SAGE_ROOT/local/lib...] ignored"
>
> On Saturday, September 23, 2023 at 3:59:40 PM UTC-7 John H Palmieri wrote:
>
>> 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 (Homebrew GCC 13.2.0) 13.2.0
>> Copyright (C) 2023 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.  There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>> PURPOSE.
>>
>> and this is the one that scipy finds. On the M2 machine, Sage's scipy
>> built back in August with earlier versions of the OS (probably 13.5.2) and
>> command-line tools and gfortran (13.1.0).
>>
>>
>> On Saturday, September 23, 2023 at 3:34:29 PM UTC-7 Dima Pasechnik wrote:
>>
>>> 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 troubleshoot it.

 On Saturday, September 23, 2023 at 2:35:52 PM UTC-7 John H Palmieri
 wrote:

> 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:
> -Dprefix=/Users/palmieri/Downloads/scipy-1.11.2/build-install
> Python system: Darwin
> The Meson build system
> Version: 1.2.1
> Source dir: /Users/palmieri/Downloads/scipy-1.11.2
> Build dir: /Users/palmieri/Downloads/scipy-1.11.2/build
> Build type: native build
> Project name: SciPy
> Project version: 1.11.2
> ---
> Detecting compiler via: `cc --version` -> 0
> stdout:
> Apple clang version 15.0.0 (clang-1500.0.40.1)
> Target: arm64-apple-darwin22.6.0
> Thread model: posix
> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
> ---
> Running command: cc -E -dM -
> -
> ---
> Detecting linker via: `cc -Wl,--version` -> 1
> stderr:
> ld: unknown options: --version
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> ---
> ---
> Detecting Apple linker via: `cc -Wl,-v` -> 1
> stderr:
> @(#)PROGRAM:ld  PROJECT:dyld-1015.7
> BUILD 18:48:48 Aug 22 2023
> configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32
> i386 x86_64 x86_64h armv6m armv7k armv7m armv7em
> will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m
> armv7k armv7m armv7em
> LTO support using: LLVM version 15.0.0 (static support for 29, runtime
> is 29)
> TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3)
> Library search paths:
> /opt/homebrew/opt/primesieve/lib
> /opt/homebrew/opt/bdw-gc/lib
> /opt/homebrew/opt/libpng/lib
> /opt/homebrew/opt/ntl/lib
> /opt/homebrew/opt/bzip2/lib
> /opt/homebrew/opt/readline/lib
> /opt/homebrew/lib
> /usr/local/lib
> Framework search paths:
> ld: Undefined symbols:
>   _main, referenced from:
>   
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> ---
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o
> sanitycheckc.exe
> Sanity check compile stdout:
>
> -
> Sanity check compile stderr:
>
> -
> Running test binary command:
>  
> /Users/palmieri/Downloads/scipy-1.11.2/build/meson-private/sanitycheckc.exe
> C compiler for the host machine: cc (clang 15.0.0 "Apple clang version
> 15.0.0 (clang-1500.0.40.1)")
> C linker for the host machine: cc ld64 1015.7
> 

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

[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 file to convince Sage that scipy had built, and the rest of 
the build succeeded, except for some extra warnings during doctests: "ld: 
warning: duplicate -rpath [...SAGE_ROOT/local/lib...] ignored"

On Saturday, September 23, 2023 at 3:59:40 PM UTC-7 John H Palmieri wrote:

> 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 (Homebrew GCC 13.2.0) 13.2.0
> Copyright (C) 2023 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> and this is the one that scipy finds. On the M2 machine, Sage's scipy 
> built back in August with earlier versions of the OS (probably 13.5.2) and 
> command-line tools and gfortran (13.1.0).
>
>
> On Saturday, September 23, 2023 at 3:34:29 PM UTC-7 Dima Pasechnik wrote:
>
>> 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 troubleshoot it.
>>>
>>> On Saturday, September 23, 2023 at 2:35:52 PM UTC-7 John H Palmieri 
>>> wrote:
>>>
 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: 
 -Dprefix=/Users/palmieri/Downloads/scipy-1.11.2/build-install
 Python system: Darwin
 The Meson build system
 Version: 1.2.1
 Source dir: /Users/palmieri/Downloads/scipy-1.11.2
 Build dir: /Users/palmieri/Downloads/scipy-1.11.2/build
 Build type: native build
 Project name: SciPy
 Project version: 1.11.2
 ---
 Detecting compiler via: `cc --version` -> 0
 stdout:
 Apple clang version 15.0.0 (clang-1500.0.40.1)
 Target: arm64-apple-darwin22.6.0
 Thread model: posix
 InstalledDir: /Library/Developer/CommandLineTools/usr/bin
 ---
 Running command: cc -E -dM -
 -
 ---
 Detecting linker via: `cc -Wl,--version` -> 1
 stderr:
 ld: unknown options: --version 
 clang: error: linker command failed with exit code 1 (use -v to see 
 invocation)
 ---
 ---
 Detecting Apple linker via: `cc -Wl,-v` -> 1
 stderr:
 @(#)PROGRAM:ld  PROJECT:dyld-1015.7
 BUILD 18:48:48 Aug 22 2023
 configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 
 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em
 will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m armv7k 
 armv7m armv7em
 LTO support using: LLVM version 15.0.0 (static support for 29, runtime 
 is 29)
 TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3)
 Library search paths:
 /opt/homebrew/opt/primesieve/lib
 /opt/homebrew/opt/bdw-gc/lib
 /opt/homebrew/opt/libpng/lib
 /opt/homebrew/opt/ntl/lib
 /opt/homebrew/opt/bzip2/lib
 /opt/homebrew/opt/readline/lib
 /opt/homebrew/lib
 /usr/local/lib
 Framework search paths:
 ld: Undefined symbols:
   _main, referenced from:
   
 clang: error: linker command failed with exit code 1 (use -v to see 
 invocation)
 ---
 Sanity testing C compiler: cc
 Is cross compiler: False.
 Sanity check compiler command line: cc sanitycheckc.c -o 
 sanitycheckc.exe
 Sanity check compile stdout:

 -
 Sanity check compile stderr:

 -
 Running test binary command: 
  
 /Users/palmieri/Downloads/scipy-1.11.2/build/meson-private/sanitycheckc.exe
 C compiler for the host machine: cc (clang 15.0.0 "Apple clang version 
 15.0.0 (clang-1500.0.40.1)")
 C linker for the host machine: cc ld64 1015.7
 ---
 Detecting linker via: `ar --version` -> 1
 stderr:
 usage:  ar -d [-TLsv] archive file ...
 ar -m [-TLsv] archive file ...
 ar -m [-abiTLsv] position archive file ...
 ar -p [-TLsv] archive [file ...]
 ar -q [-cTLsv] archive file ...
 ar -r [-cuTLsv] archive file ...
 ar -r [-abciuTLsv] position archive file ...
 ar -t [-TLsv] archive [file ...]
 ar -x [-ouTLsv] archive 

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

[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 (Homebrew GCC 13.2.0) 13.2.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

and this is the one that scipy finds. On the M2 machine, Sage's scipy built 
back in August with earlier versions of the OS (probably 13.5.2) and 
command-line tools and gfortran (13.1.0).


On Saturday, September 23, 2023 at 3:34:29 PM UTC-7 Dima Pasechnik wrote:

> 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 troubleshoot it.
>>
>> On Saturday, September 23, 2023 at 2:35:52 PM UTC-7 John H Palmieri wrote:
>>
>>> 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: 
>>> -Dprefix=/Users/palmieri/Downloads/scipy-1.11.2/build-install
>>> Python system: Darwin
>>> The Meson build system
>>> Version: 1.2.1
>>> Source dir: /Users/palmieri/Downloads/scipy-1.11.2
>>> Build dir: /Users/palmieri/Downloads/scipy-1.11.2/build
>>> Build type: native build
>>> Project name: SciPy
>>> Project version: 1.11.2
>>> ---
>>> Detecting compiler via: `cc --version` -> 0
>>> stdout:
>>> Apple clang version 15.0.0 (clang-1500.0.40.1)
>>> Target: arm64-apple-darwin22.6.0
>>> Thread model: posix
>>> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
>>> ---
>>> Running command: cc -E -dM -
>>> -
>>> ---
>>> Detecting linker via: `cc -Wl,--version` -> 1
>>> stderr:
>>> ld: unknown options: --version 
>>> clang: error: linker command failed with exit code 1 (use -v to see 
>>> invocation)
>>> ---
>>> ---
>>> Detecting Apple linker via: `cc -Wl,-v` -> 1
>>> stderr:
>>> @(#)PROGRAM:ld  PROJECT:dyld-1015.7
>>> BUILD 18:48:48 Aug 22 2023
>>> configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 
>>> i386 x86_64 x86_64h armv6m armv7k armv7m armv7em
>>> will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m armv7k 
>>> armv7m armv7em
>>> LTO support using: LLVM version 15.0.0 (static support for 29, runtime 
>>> is 29)
>>> TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3)
>>> Library search paths:
>>> /opt/homebrew/opt/primesieve/lib
>>> /opt/homebrew/opt/bdw-gc/lib
>>> /opt/homebrew/opt/libpng/lib
>>> /opt/homebrew/opt/ntl/lib
>>> /opt/homebrew/opt/bzip2/lib
>>> /opt/homebrew/opt/readline/lib
>>> /opt/homebrew/lib
>>> /usr/local/lib
>>> Framework search paths:
>>> ld: Undefined symbols:
>>>   _main, referenced from:
>>>   
>>> clang: error: linker command failed with exit code 1 (use -v to see 
>>> invocation)
>>> ---
>>> Sanity testing C compiler: cc
>>> Is cross compiler: False.
>>> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe
>>> Sanity check compile stdout:
>>>
>>> -
>>> Sanity check compile stderr:
>>>
>>> -
>>> Running test binary command: 
>>>  /Users/palmieri/Downloads/scipy-1.11.2/build/meson-private/sanitycheckc.exe
>>> C compiler for the host machine: cc (clang 15.0.0 "Apple clang version 
>>> 15.0.0 (clang-1500.0.40.1)")
>>> C linker for the host machine: cc ld64 1015.7
>>> ---
>>> Detecting linker via: `ar --version` -> 1
>>> stderr:
>>> usage:  ar -d [-TLsv] archive file ...
>>> ar -m [-TLsv] archive file ...
>>> ar -m [-abiTLsv] position archive file ...
>>> ar -p [-TLsv] archive [file ...]
>>> ar -q [-cTLsv] archive file ...
>>> ar -r [-cuTLsv] archive file ...
>>> ar -r [-abciuTLsv] position archive file ...
>>> ar -t [-TLsv] archive [file ...]
>>> ar -x [-ouTLsv] archive [file ...]
>>> ---
>>> ---
>>> Detecting compiler via: `c++ --version` -> 0
>>> stdout:
>>> Apple clang version 15.0.0 (clang-1500.0.40.1)
>>> Target: arm64-apple-darwin22.6.0
>>> Thread model: posix
>>> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
>>> ---
>>> Running command: c++ -E -dM -
>>> -
>>> ---
>>> Detecting linker via: `c++ -Wl,--version` -> 1
>>> stderr:
>>> ld: unknown options: --version 
>>> clang: error: linker command failed with exit code 1 (use -v to see 
>>> invocation)
>>> ---
>>> ---
>>> Detecting Apple linker via: `c++ -Wl,-v` -> 1
>>> stderr:
>>> @(#)PROGRAM:ld  PROJECT:dyld-1015.7
>>> BUILD 18:48:48 Aug 22 2023
>>> 

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

[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 troubleshoot it.
>
> On Saturday, September 23, 2023 at 2:35:52 PM UTC-7 John H Palmieri wrote:
>
>> 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:
>> -Dprefix=/Users/palmieri/Downloads/scipy-1.11.2/build-install
>> Python system: Darwin
>> The Meson build system
>> Version: 1.2.1
>> Source dir: /Users/palmieri/Downloads/scipy-1.11.2
>> Build dir: /Users/palmieri/Downloads/scipy-1.11.2/build
>> Build type: native build
>> Project name: SciPy
>> Project version: 1.11.2
>> ---
>> Detecting compiler via: `cc --version` -> 0
>> stdout:
>> Apple clang version 15.0.0 (clang-1500.0.40.1)
>> Target: arm64-apple-darwin22.6.0
>> Thread model: posix
>> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
>> ---
>> Running command: cc -E -dM -
>> -
>> ---
>> Detecting linker via: `cc -Wl,--version` -> 1
>> stderr:
>> ld: unknown options: --version
>> clang: error: linker command failed with exit code 1 (use -v to see
>> invocation)
>> ---
>> ---
>> Detecting Apple linker via: `cc -Wl,-v` -> 1
>> stderr:
>> @(#)PROGRAM:ld  PROJECT:dyld-1015.7
>> BUILD 18:48:48 Aug 22 2023
>> configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32
>> i386 x86_64 x86_64h armv6m armv7k armv7m armv7em
>> will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m armv7k
>> armv7m armv7em
>> LTO support using: LLVM version 15.0.0 (static support for 29, runtime is
>> 29)
>> TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3)
>> Library search paths:
>> /opt/homebrew/opt/primesieve/lib
>> /opt/homebrew/opt/bdw-gc/lib
>> /opt/homebrew/opt/libpng/lib
>> /opt/homebrew/opt/ntl/lib
>> /opt/homebrew/opt/bzip2/lib
>> /opt/homebrew/opt/readline/lib
>> /opt/homebrew/lib
>> /usr/local/lib
>> Framework search paths:
>> ld: Undefined symbols:
>>   _main, referenced from:
>>   
>> clang: error: linker command failed with exit code 1 (use -v to see
>> invocation)
>> ---
>> Sanity testing C compiler: cc
>> Is cross compiler: False.
>> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe
>> Sanity check compile stdout:
>>
>> -
>> Sanity check compile stderr:
>>
>> -
>> Running test binary command:
>>  /Users/palmieri/Downloads/scipy-1.11.2/build/meson-private/sanitycheckc.exe
>> C compiler for the host machine: cc (clang 15.0.0 "Apple clang version
>> 15.0.0 (clang-1500.0.40.1)")
>> C linker for the host machine: cc ld64 1015.7
>> ---
>> Detecting linker via: `ar --version` -> 1
>> stderr:
>> usage:  ar -d [-TLsv] archive file ...
>> ar -m [-TLsv] archive file ...
>> ar -m [-abiTLsv] position archive file ...
>> ar -p [-TLsv] archive [file ...]
>> ar -q [-cTLsv] archive file ...
>> ar -r [-cuTLsv] archive file ...
>> ar -r [-abciuTLsv] position archive file ...
>> ar -t [-TLsv] archive [file ...]
>> ar -x [-ouTLsv] archive [file ...]
>> ---
>> ---
>> Detecting compiler via: `c++ --version` -> 0
>> stdout:
>> Apple clang version 15.0.0 (clang-1500.0.40.1)
>> Target: arm64-apple-darwin22.6.0
>> Thread model: posix
>> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
>> ---
>> Running command: c++ -E -dM -
>> -
>> ---
>> Detecting linker via: `c++ -Wl,--version` -> 1
>> stderr:
>> ld: unknown options: --version
>> clang: error: linker command failed with exit code 1 (use -v to see
>> invocation)
>> ---
>> ---
>> Detecting Apple linker via: `c++ -Wl,-v` -> 1
>> stderr:
>> @(#)PROGRAM:ld  PROJECT:dyld-1015.7
>> BUILD 18:48:48 Aug 22 2023
>> configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32
>> i386 x86_64 x86_64h armv6m armv7k armv7m armv7em
>> will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m armv7k
>> armv7m armv7em
>> LTO support using: LLVM version 15.0.0 (static support for 29, runtime is
>> 29)
>> TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3)
>> Library search paths:
>> /opt/homebrew/opt/primesieve/lib
>> /opt/homebrew/opt/bdw-gc/lib
>> /opt/homebrew/opt/libpng/lib
>> /opt/homebrew/opt/ntl/lib
>> /opt/homebrew/opt/bzip2/lib
>> /opt/homebrew/opt/readline/lib
>> /opt/homebrew/lib
>> /usr/local/lib
>> Framework search paths:
>> ld: Undefined symbols:
>>   _main, referenced from:
>>   
>> clang: error: linker command failed with exit code 1 (use -v to see
>> invocation)
>> ---
>> Sanity testing C++ compiler: c++
>> Is cross compiler: False.
>> Sanity check compiler command line: c++ 

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

[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 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: 
> -Dprefix=/Users/palmieri/Downloads/scipy-1.11.2/build-install
> Python system: Darwin
> The Meson build system
> Version: 1.2.1
> Source dir: /Users/palmieri/Downloads/scipy-1.11.2
> Build dir: /Users/palmieri/Downloads/scipy-1.11.2/build
> Build type: native build
> Project name: SciPy
> Project version: 1.11.2
> ---
> Detecting compiler via: `cc --version` -> 0
> stdout:
> Apple clang version 15.0.0 (clang-1500.0.40.1)
> Target: arm64-apple-darwin22.6.0
> Thread model: posix
> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
> ---
> Running command: cc -E -dM -
> -
> ---
> Detecting linker via: `cc -Wl,--version` -> 1
> stderr:
> ld: unknown options: --version 
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> ---
> ---
> Detecting Apple linker via: `cc -Wl,-v` -> 1
> stderr:
> @(#)PROGRAM:ld  PROJECT:dyld-1015.7
> BUILD 18:48:48 Aug 22 2023
> configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 
> x86_64 x86_64h armv6m armv7k armv7m armv7em
> will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m armv7k 
> armv7m armv7em
> LTO support using: LLVM version 15.0.0 (static support for 29, runtime is 
> 29)
> TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3)
> Library search paths:
> /opt/homebrew/opt/primesieve/lib
> /opt/homebrew/opt/bdw-gc/lib
> /opt/homebrew/opt/libpng/lib
> /opt/homebrew/opt/ntl/lib
> /opt/homebrew/opt/bzip2/lib
> /opt/homebrew/opt/readline/lib
> /opt/homebrew/lib
> /usr/local/lib
> Framework search paths:
> ld: Undefined symbols:
>   _main, referenced from:
>   
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> ---
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe
> Sanity check compile stdout:
>
> -
> Sanity check compile stderr:
>
> -
> Running test binary command: 
>  /Users/palmieri/Downloads/scipy-1.11.2/build/meson-private/sanitycheckc.exe
> C compiler for the host machine: cc (clang 15.0.0 "Apple clang version 
> 15.0.0 (clang-1500.0.40.1)")
> C linker for the host machine: cc ld64 1015.7
> ---
> Detecting linker via: `ar --version` -> 1
> stderr:
> usage:  ar -d [-TLsv] archive file ...
> ar -m [-TLsv] archive file ...
> ar -m [-abiTLsv] position archive file ...
> ar -p [-TLsv] archive [file ...]
> ar -q [-cTLsv] archive file ...
> ar -r [-cuTLsv] archive file ...
> ar -r [-abciuTLsv] position archive file ...
> ar -t [-TLsv] archive [file ...]
> ar -x [-ouTLsv] archive [file ...]
> ---
> ---
> Detecting compiler via: `c++ --version` -> 0
> stdout:
> Apple clang version 15.0.0 (clang-1500.0.40.1)
> Target: arm64-apple-darwin22.6.0
> Thread model: posix
> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
> ---
> Running command: c++ -E -dM -
> -
> ---
> Detecting linker via: `c++ -Wl,--version` -> 1
> stderr:
> ld: unknown options: --version 
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> ---
> ---
> Detecting Apple linker via: `c++ -Wl,-v` -> 1
> stderr:
> @(#)PROGRAM:ld  PROJECT:dyld-1015.7
> BUILD 18:48:48 Aug 22 2023
> configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 
> x86_64 x86_64h armv6m armv7k armv7m armv7em
> will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m armv7k 
> armv7m armv7em
> LTO support using: LLVM version 15.0.0 (static support for 29, runtime is 
> 29)
> TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3)
> Library search paths:
> /opt/homebrew/opt/primesieve/lib
> /opt/homebrew/opt/bdw-gc/lib
> /opt/homebrew/opt/libpng/lib
> /opt/homebrew/opt/ntl/lib
> /opt/homebrew/opt/bzip2/lib
> /opt/homebrew/opt/readline/lib
> /opt/homebrew/lib
> /usr/local/lib
> Framework search paths:
> ld: Undefined symbols:
>   _main, referenced from:
>   
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> ---
> Sanity testing C++ compiler: c++
> Is cross compiler: False.
> Sanity check compiler command line: c++ sanitycheckcpp.cc -o 
> sanitycheckcpp.exe
> Sanity check compile stdout:
>
> -
> Sanity check compile stderr:
>
> -
> Running test binary command: 
>  

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

[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: -Dprefix=/Users/palmieri/Downloads/scipy-1.11.2/build-install
Python system: Darwin
The Meson build system
Version: 1.2.1
Source dir: /Users/palmieri/Downloads/scipy-1.11.2
Build dir: /Users/palmieri/Downloads/scipy-1.11.2/build
Build type: native build
Project name: SciPy
Project version: 1.11.2
---
Detecting compiler via: `cc --version` -> 0
stdout:
Apple clang version 15.0.0 (clang-1500.0.40.1)
Target: arm64-apple-darwin22.6.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
---
Running command: cc -E -dM -
-
---
Detecting linker via: `cc -Wl,--version` -> 1
stderr:
ld: unknown options: --version 
clang: error: linker command failed with exit code 1 (use -v to see 
invocation)
---
---
Detecting Apple linker via: `cc -Wl,-v` -> 1
stderr:
@(#)PROGRAM:ld  PROJECT:dyld-1015.7
BUILD 18:48:48 Aug 22 2023
configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 
x86_64 x86_64h armv6m armv7k armv7m armv7em
will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m armv7k 
armv7m armv7em
LTO support using: LLVM version 15.0.0 (static support for 29, runtime is 
29)
TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3)
Library search paths:
/opt/homebrew/opt/primesieve/lib
/opt/homebrew/opt/bdw-gc/lib
/opt/homebrew/opt/libpng/lib
/opt/homebrew/opt/ntl/lib
/opt/homebrew/opt/bzip2/lib
/opt/homebrew/opt/readline/lib
/opt/homebrew/lib
/usr/local/lib
Framework search paths:
ld: Undefined symbols:
  _main, referenced from:
  
clang: error: linker command failed with exit code 1 (use -v to see 
invocation)
---
Sanity testing C compiler: cc
Is cross compiler: False.
Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe
Sanity check compile stdout:

-
Sanity check compile stderr:

-
Running test binary command: 
 /Users/palmieri/Downloads/scipy-1.11.2/build/meson-private/sanitycheckc.exe
C compiler for the host machine: cc (clang 15.0.0 "Apple clang version 
15.0.0 (clang-1500.0.40.1)")
C linker for the host machine: cc ld64 1015.7
---
Detecting linker via: `ar --version` -> 1
stderr:
usage:  ar -d [-TLsv] archive file ...
ar -m [-TLsv] archive file ...
ar -m [-abiTLsv] position archive file ...
ar -p [-TLsv] archive [file ...]
ar -q [-cTLsv] archive file ...
ar -r [-cuTLsv] archive file ...
ar -r [-abciuTLsv] position archive file ...
ar -t [-TLsv] archive [file ...]
ar -x [-ouTLsv] archive [file ...]
---
---
Detecting compiler via: `c++ --version` -> 0
stdout:
Apple clang version 15.0.0 (clang-1500.0.40.1)
Target: arm64-apple-darwin22.6.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
---
Running command: c++ -E -dM -
-
---
Detecting linker via: `c++ -Wl,--version` -> 1
stderr:
ld: unknown options: --version 
clang: error: linker command failed with exit code 1 (use -v to see 
invocation)
---
---
Detecting Apple linker via: `c++ -Wl,-v` -> 1
stderr:
@(#)PROGRAM:ld  PROJECT:dyld-1015.7
BUILD 18:48:48 Aug 22 2023
configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 
x86_64 x86_64h armv6m armv7k armv7m armv7em
will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m armv7k 
armv7m armv7em
LTO support using: LLVM version 15.0.0 (static support for 29, runtime is 
29)
TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3)
Library search paths:
/opt/homebrew/opt/primesieve/lib
/opt/homebrew/opt/bdw-gc/lib
/opt/homebrew/opt/libpng/lib
/opt/homebrew/opt/ntl/lib
/opt/homebrew/opt/bzip2/lib
/opt/homebrew/opt/readline/lib
/opt/homebrew/lib
/usr/local/lib
Framework search paths:
ld: Undefined symbols:
  _main, referenced from:
  
clang: error: linker command failed with exit code 1 (use -v to see 
invocation)
---
Sanity testing C++ compiler: c++
Is cross compiler: False.
Sanity check compiler command line: c++ sanitycheckcpp.cc -o 
sanitycheckcpp.exe
Sanity check compile stdout:

-
Sanity check compile stderr:

-
Running test binary command: 
 /Users/palmieri/Downloads/scipy-1.11.2/build/meson-private/sanitycheckcpp.exe
C++ compiler for the host machine: c++ (clang 15.0.0 "Apple clang version 
15.0.0 (clang-1500.0.40.1)")
C++ linker for the host machine: c++ ld64 1015.7
---
Detecting compiler via: `cython -V` -> 0
stdout:
Cython version 3.0.2
---
stderr:
Cython version 3.0.2
---
Running compile:
Working directory: 
 /var/folders/_y/kzsymttn15l00trk8fbjfj88gn/T/tmp7o4nw2zx
Code:
 print("hello world")
---
Command line: `cython 
/var/folders/_y/kzsymttn15l00trk8fbjfj88gn/T/tmp7o4nw2zx/testfile.pyx 
-o 

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

[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 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 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 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 Thursday, September 21, 2023 at 11:18:15 PM UTC-7 Dima Pasechnik
 wrote:

> 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 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
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib`
>>   stdout:
>>   stderr: collect2 version 13.2.0
>>   /usr/bin/ld -syslibroot
>> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/ -dynamic -arch 
>> arm64
>> -platform_version macos 13.0.0 0.0 -o a.out
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>> -L/opt/homebrew/opt/primesieve/lib -L/opt/homebrew/opt/bdw-gc/lib
>> -L/opt/homebrew/opt/libpng/lib -L/opt/homebrew/opt/ntl/lib
>> -L/opt/homebrew/opt/bzip2/lib -L/opt/homebrew/opt/readline/lib
>> -L/opt/homebrew/lib
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13/../../..
>> --version -rpath
>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -lemutls_w
>> -lgcc -lSystem -lgcc -no_compact_unwind -rpath @loader_path -rpath
>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc/aarch64-apple-darwin22/13
>> -rpath /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc -rpath
>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>> /opt/homebrew/Cellar/primesieve/11.1/lib -rpath
>> /opt/homebrew/Cellar/bdw-gc/8.2.4/lib -rpath
>> /opt/homebrew/Cellar/libpng/1.6.40/lib -rpath
>> /opt/homebrew/Cellar/ntl/11.5.1/lib -rpath
>> /opt/homebrew/Cellar/bzip2/1.0.8/lib -rpath
>> /opt/homebrew/Cellar/readline/8.2.1/lib -rpath /opt/homebrew/lib -rpath
>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current
>>   ld: unknown options: --version
>>   collect2: error: ld returned 1 exit status
>>
>> Suggestions?
>>
>> On Sunday, September 17, 2023 at 11:25:02 AM UTC-7 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" succeeds, as does "make".
>>>
>>>
>>>
>>> On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee
>>> wrote:
>>>
 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] 
> [sagelib-10.2.beta3]

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

[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 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 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 Thursday, September 21, 2023 at 11:18:15 PM UTC-7 Dima Pasechnik 
>>> wrote:
>>>
 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 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 
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib`
>   stdout:
>   stderr: collect2 version 13.2.0
>   /usr/bin/ld -syslibroot 
> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/ -dynamic -arch 
> arm64 
> -platform_version macos 13.0.0 0.0 -o a.out 
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13
>  
> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc 
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
> -L/opt/homebrew/opt/primesieve/lib -L/opt/homebrew/opt/bdw-gc/lib 
> -L/opt/homebrew/opt/libpng/lib -L/opt/homebrew/opt/ntl/lib 
> -L/opt/homebrew/opt/bzip2/lib -L/opt/homebrew/opt/readline/lib 
> -L/opt/homebrew/lib 
> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13/../../..
>  
> --version -rpath 
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath 
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -lemutls_w 
> -lgcc -lSystem -lgcc -no_compact_unwind -rpath @loader_path -rpath 
> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc/aarch64-apple-darwin22/13
>  
> -rpath /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc -rpath 
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath 
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath 
> /opt/homebrew/Cellar/primesieve/11.1/lib -rpath 
> /opt/homebrew/Cellar/bdw-gc/8.2.4/lib -rpath 
> /opt/homebrew/Cellar/libpng/1.6.40/lib -rpath 
> /opt/homebrew/Cellar/ntl/11.5.1/lib -rpath 
> /opt/homebrew/Cellar/bzip2/1.0.8/lib -rpath 
> /opt/homebrew/Cellar/readline/8.2.1/lib -rpath /opt/homebrew/lib -rpath 
> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current
>   ld: unknown options: --version
>   collect2: error: ld returned 1 exit status
>
> Suggestions?
>
> On Sunday, September 17, 2023 at 11:25:02 AM UTC-7 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" succeeds, as does "make".
>>
>>
>>
>> On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
>>
>>> 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] 
 [sagelib-10.2.beta3]   Removing file or directory 
 /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
 [sagelib-10.2.beta3]   Removing pth entries from 

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

[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 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 Thursday, September 21, 2023 at 11:18:15 PM UTC-7 Dima Pasechnik wrote:
>>
>>> 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 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 
 -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
 -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
 -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
 -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib`
   stdout:
   stderr: collect2 version 13.2.0
   /usr/bin/ld -syslibroot 
 /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/ -dynamic -arch 
 arm64 
 -platform_version macos 13.0.0 0.0 -o a.out 
 -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
 -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
 -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13
  
 -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc 
 -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
 -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
 -L/opt/homebrew/opt/primesieve/lib -L/opt/homebrew/opt/bdw-gc/lib 
 -L/opt/homebrew/opt/libpng/lib -L/opt/homebrew/opt/ntl/lib 
 -L/opt/homebrew/opt/bzip2/lib -L/opt/homebrew/opt/readline/lib 
 -L/opt/homebrew/lib 
 -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13/../../..
  
 --version -rpath 
 /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath 
 /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -lemutls_w 
 -lgcc -lSystem -lgcc -no_compact_unwind -rpath @loader_path -rpath 
 /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc/aarch64-apple-darwin22/13
  
 -rpath /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc -rpath 
 /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath 
 /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath 
 /opt/homebrew/Cellar/primesieve/11.1/lib -rpath 
 /opt/homebrew/Cellar/bdw-gc/8.2.4/lib -rpath 
 /opt/homebrew/Cellar/libpng/1.6.40/lib -rpath 
 /opt/homebrew/Cellar/ntl/11.5.1/lib -rpath 
 /opt/homebrew/Cellar/bzip2/1.0.8/lib -rpath 
 /opt/homebrew/Cellar/readline/8.2.1/lib -rpath /opt/homebrew/lib -rpath 
 /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current
   ld: unknown options: --version
   collect2: error: ld returned 1 exit status

 Suggestions?

 On Sunday, September 17, 2023 at 11:25:02 AM UTC-7 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" succeeds, as does "make".
>
>
>
> On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
>
>> 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] 
>>> [sagelib-10.2.beta3]   Removing file or directory 
>>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
>>> [sagelib-10.2.beta3]   Removing pth entries from 
>>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
>>> [sagelib-10.2.beta3]   Removing entry: 
>>> /Users/kwankyu/GitHub/sage-dev/src
>>> [sagelib-10.2.beta3]   

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

[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 the cached download file for homebrew's gcc
> and tried again, same result. I have not yet tried Sage's gcc.
>
> On Thursday, September 21, 2023 at 11:18:15 PM UTC-7 Dima Pasechnik wrote:
>
>> 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 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
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib`
>>>   stdout:
>>>   stderr: collect2 version 13.2.0
>>>   /usr/bin/ld -syslibroot
>>> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/ -dynamic -arch arm64
>>> -platform_version macos 13.0.0 0.0 -o a.out
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13
>>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -L/opt/homebrew/opt/primesieve/lib -L/opt/homebrew/opt/bdw-gc/lib
>>> -L/opt/homebrew/opt/libpng/lib -L/opt/homebrew/opt/ntl/lib
>>> -L/opt/homebrew/opt/bzip2/lib -L/opt/homebrew/opt/readline/lib
>>> -L/opt/homebrew/lib
>>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13/../../..
>>> --version -rpath
>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -lemutls_w
>>> -lgcc -lSystem -lgcc -no_compact_unwind -rpath @loader_path -rpath
>>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc/aarch64-apple-darwin22/13
>>> -rpath /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc -rpath
>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>>> /opt/homebrew/Cellar/primesieve/11.1/lib -rpath
>>> /opt/homebrew/Cellar/bdw-gc/8.2.4/lib -rpath
>>> /opt/homebrew/Cellar/libpng/1.6.40/lib -rpath
>>> /opt/homebrew/Cellar/ntl/11.5.1/lib -rpath
>>> /opt/homebrew/Cellar/bzip2/1.0.8/lib -rpath
>>> /opt/homebrew/Cellar/readline/8.2.1/lib -rpath /opt/homebrew/lib -rpath
>>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current
>>>   ld: unknown options: --version
>>>   collect2: error: ld returned 1 exit status
>>>
>>> Suggestions?
>>>
>>> On Sunday, September 17, 2023 at 11:25:02 AM UTC-7 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" succeeds, as does "make".



 On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:

> 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] 
>> [sagelib-10.2.beta3]   Removing file or directory
>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
>> [sagelib-10.2.beta3]   Removing pth entries from
>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
>> [sagelib-10.2.beta3]   Removing entry:
>> /Users/kwankyu/GitHub/sage-dev/src
>> [sagelib-10.2.beta3]   Successfully uninstalled
>> sagemath-standard-10.2b3
>> [sagelib-10.2.beta3]   Running setup.py develop for sagemath-standard
>> [sagelib-10.2.beta3] Running command python setup.py develop
>> [scipy-1.11.2] Setting up build directory for scipy-1.11.2
>> [scipy-1.11.2] Finished extraction
>> [scipy-1.11.2] 

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

[John H Palmieri]

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 Thursday, September 21, 2023 at 11:18:15 PM UTC-7 Dima Pasechnik wrote:

> 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 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 
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
>> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
>> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib`
>>   stdout:
>>   stderr: collect2 version 13.2.0
>>   /usr/bin/ld -syslibroot 
>> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/ -dynamic -arch arm64 
>> -platform_version macos 13.0.0 0.0 -o a.out 
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13
>>  
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc 
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib 
>> -L/opt/homebrew/opt/primesieve/lib -L/opt/homebrew/opt/bdw-gc/lib 
>> -L/opt/homebrew/opt/libpng/lib -L/opt/homebrew/opt/ntl/lib 
>> -L/opt/homebrew/opt/bzip2/lib -L/opt/homebrew/opt/readline/lib 
>> -L/opt/homebrew/lib 
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13/../../..
>>  
>> --version -rpath 
>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath 
>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -lemutls_w 
>> -lgcc -lSystem -lgcc -no_compact_unwind -rpath @loader_path -rpath 
>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc/aarch64-apple-darwin22/13
>>  
>> -rpath /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc -rpath 
>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath 
>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath 
>> /opt/homebrew/Cellar/primesieve/11.1/lib -rpath 
>> /opt/homebrew/Cellar/bdw-gc/8.2.4/lib -rpath 
>> /opt/homebrew/Cellar/libpng/1.6.40/lib -rpath 
>> /opt/homebrew/Cellar/ntl/11.5.1/lib -rpath 
>> /opt/homebrew/Cellar/bzip2/1.0.8/lib -rpath 
>> /opt/homebrew/Cellar/readline/8.2.1/lib -rpath /opt/homebrew/lib -rpath 
>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current
>>   ld: unknown options: --version
>>   collect2: error: ld returned 1 exit status
>>
>> Suggestions?
>>
>> On Sunday, September 17, 2023 at 11:25:02 AM UTC-7 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" succeeds, as does "make".
>>>
>>>
>>>
>>> On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
>>>
 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] 
> [sagelib-10.2.beta3]   Removing file or directory 
> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
> [sagelib-10.2.beta3]   Removing pth entries from 
> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
> [sagelib-10.2.beta3]   Removing entry: 
> /Users/kwankyu/GitHub/sage-dev/src
> [sagelib-10.2.beta3]   Successfully uninstalled 
> sagemath-standard-10.2b3
> [sagelib-10.2.beta3]   Running setup.py develop for sagemath-standard
> [sagelib-10.2.beta3] Running command python setup.py develop
> [scipy-1.11.2] Setting up build directory for scipy-1.11.2
> [scipy-1.11.2] Finished extraction
> [scipy-1.11.2] Applying patches from ../patches...
> [scipy-1.11.2] Applying ../patches/numpy-include.patch
> [scipy-1.11.2] patching file scipy/spatial/setup.py
> 

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

[Dima Pasechnik]

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 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
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib`
>   stdout:
>   stderr: collect2 version 13.2.0
>   /usr/bin/ld -syslibroot
> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/ -dynamic -arch arm64
> -platform_version macos 13.0.0 0.0 -o a.out
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13
> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -L/opt/homebrew/opt/primesieve/lib -L/opt/homebrew/opt/bdw-gc/lib
> -L/opt/homebrew/opt/libpng/lib -L/opt/homebrew/opt/ntl/lib
> -L/opt/homebrew/opt/bzip2/lib -L/opt/homebrew/opt/readline/lib
> -L/opt/homebrew/lib
> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13/../../..
> --version -rpath
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -lemutls_w
> -lgcc -lSystem -lgcc -no_compact_unwind -rpath @loader_path -rpath
> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc/aarch64-apple-darwin22/13
> -rpath /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc -rpath
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
> /opt/homebrew/Cellar/primesieve/11.1/lib -rpath
> /opt/homebrew/Cellar/bdw-gc/8.2.4/lib -rpath
> /opt/homebrew/Cellar/libpng/1.6.40/lib -rpath
> /opt/homebrew/Cellar/ntl/11.5.1/lib -rpath
> /opt/homebrew/Cellar/bzip2/1.0.8/lib -rpath
> /opt/homebrew/Cellar/readline/8.2.1/lib -rpath /opt/homebrew/lib -rpath
> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current
>   ld: unknown options: --version
>   collect2: error: ld returned 1 exit status
>
> Suggestions?
>
> On Sunday, September 17, 2023 at 11:25:02 AM UTC-7 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" succeeds, as does "make".
>>
>>
>>
>> On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
>>
>>> 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] 
 [sagelib-10.2.beta3]   Removing file or directory
 /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
 [sagelib-10.2.beta3]   Removing pth entries from
 /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
 [sagelib-10.2.beta3]   Removing entry:
 /Users/kwankyu/GitHub/sage-dev/src
 [sagelib-10.2.beta3]   Successfully uninstalled
 sagemath-standard-10.2b3
 [sagelib-10.2.beta3]   Running setup.py develop for sagemath-standard
 [sagelib-10.2.beta3] Running command python setup.py develop
 [scipy-1.11.2] Setting up build directory for scipy-1.11.2
 [scipy-1.11.2] Finished extraction
 [scipy-1.11.2] Applying patches from ../patches...
 [scipy-1.11.2] Applying ../patches/numpy-include.patch
 [scipy-1.11.2] patching file scipy/spatial/setup.py
 [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines).
 [scipy-1.11.2] Applying ../patches/tests_no_internet_dependency.patch
 [scipy-1.11.2] patching file scipy/datasets/meson.build
 [scipy-1.11.2] 
 [scipy-1.11.2] Host system:
 [scipy-1.11.2] Darwin Helios.local 22.6.0 Darwin Kernel Version 22.6.0:
 Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64
 [scipy-1.11.2] 

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

[John Cremona]

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 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 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'
> >>> + printf '%s\n' 'no; skipping check'
> >>> + sage_spkg_install_meson-python=yes
> >>> ./configure: line 49870: sage_spkg_install_meson-python=yes: command
> not found
> >>> + test yes = yes
> >>> + :
> >>> + sage_use_system_meson-python=no
> >>> ./configure: line 49874: sage_use_system_meson-python=no: command not
> found
> >>> + test xno = xno
> >>> + :
> >>> + sage_use_system_meson_python=yes
> >>> + printf '%s\n' 'configure:49884: will use system package and not
> install SPKG meson_python'
> >>> + printf '%s\n' 'configure: will use system package and not install
> SPKG meson_python'
> >>> +
> >>>
> >>> On Sunday, September 17, 2023 at 1:34:35 PM UTC-7 Dima Pasechnik wrote:
> 
> 
> 
>  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" succeeds, as does "make".
> 
>  $ cat build/pkgs/scipy/dependencies
>   $(BLAS) gfortran numpy pybind11 cython pythran | $(PYTHON_TOOLCHAIN)
> meson_python $(PYTHON)
> 
>  looks OK. So this looks like a bug in our build system
> 
> 
>  >
>  >
>  >
>  > On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee
> wrote:
>  >>
>  >> 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]
> 
>  >>> [sagelib-10.2.beta3]   Removing file or directory
> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
>  >>> [sagelib-10.2.beta3]   Removing pth entries from
> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
>  >>> [sagelib-10.2.beta3]   Removing entry:
> /Users/kwankyu/GitHub/sage-dev/src
>  >>> [sagelib-10.2.beta3]   Successfully uninstalled
> sagemath-standard-10.2b3
>  >>> [sagelib-10.2.beta3]   Running setup.py develop for
> sagemath-standard
>  >>> [sagelib-10.2.beta3] Running command python setup.py develop
>  >>> [scipy-1.11.2] Setting up build directory for scipy-1.11.2
>  >>> [scipy-1.11.2] Finished extraction
>  >>> [scipy-1.11.2] Applying patches from ../patches...
>  >>> [scipy-1.11.2] Applying ../patches/numpy-include.patch
>  >>> [scipy-1.11.2] patching file scipy/spatial/setup.py
>  >>> [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines).
>  >>> [scipy-1.11.2] Applying
> ../patches/tests_no_internet_dependency.patch
>  >>> [scipy-1.11.2] patching file scipy/datasets/meson.build
>  >>> [scipy-1.11.2]
> 
>  >>> [scipy-1.11.2] Host system:
>  >>> [scipy-1.11.2] Darwin Helios.local 22.6.0 Darwin Kernel Version
> 22.6.0: Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64
> x86_64
>  >>> [scipy-1.11.2]
> 
>  >>> [scipy-1.11.2] C compiler: gcc
>  >>> [scipy-1.11.2] C compiler version:
>  >>> [scipy-1.11.2] Apple clang version 14.0.3 (clang-1403.0.22.14.1)
>  >>> [scipy-1.11.2] Target: x86_64-apple-darwin22.6.0
>  >>> [scipy-1.11.2] Thread model: posix
>  >>> [scipy-1.11.2] InstalledDir:
> /Library/Developer/CommandLineTools/usr/bin
>  >>> [scipy-1.11.2]
> 
>  >>> [scipy-1.11.2] Package 'scipy' is currently not installed
>  >>> [scipy-1.11.2] No legacy uninstaller found for 'scipy'; nothing
> to do
>  >>> [scipy-1.11.2] Installing scipy-1.11.2
>  >>> 

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

[Dima Pasechnik]

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 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 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'
>>> + printf '%s\n' 'no; skipping check'
>>> + sage_spkg_install_meson-python=yes
>>> ./configure: line 49870: sage_spkg_install_meson-python=yes: command not 
>>> found
>>> + test yes = yes
>>> + :
>>> + sage_use_system_meson-python=no
>>> ./configure: line 49874: sage_use_system_meson-python=no: command not found
>>> + test xno = xno
>>> + :
>>> + sage_use_system_meson_python=yes
>>> + printf '%s\n' 'configure:49884: will use system package and not install 
>>> SPKG meson_python'
>>> + printf '%s\n' 'configure: will use system package and not install SPKG 
>>> meson_python'
>>> +
>>>
>>> On Sunday, September 17, 2023 at 1:34:35 PM UTC-7 Dima Pasechnik wrote:



 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" succeeds, as does "make".

 $ cat build/pkgs/scipy/dependencies
  $(BLAS) gfortran numpy pybind11 cython pythran | $(PYTHON_TOOLCHAIN) 
 meson_python $(PYTHON)

 looks OK. So this looks like a bug in our build system


 >
 >
 >
 > On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
 >>
 >> 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] 
 >>> [sagelib-10.2.beta3]   Removing file or directory 
 >>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
 >>> [sagelib-10.2.beta3]   Removing pth entries from 
 >>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
 >>> [sagelib-10.2.beta3]   Removing entry: 
 >>> /Users/kwankyu/GitHub/sage-dev/src
 >>> [sagelib-10.2.beta3]   Successfully uninstalled 
 >>> sagemath-standard-10.2b3
 >>> [sagelib-10.2.beta3]   Running setup.py develop for sagemath-standard
 >>> [sagelib-10.2.beta3] Running command python setup.py develop
 >>> [scipy-1.11.2] Setting up build directory for scipy-1.11.2
 >>> [scipy-1.11.2] Finished extraction
 >>> [scipy-1.11.2] Applying patches from ../patches...
 >>> [scipy-1.11.2] Applying ../patches/numpy-include.patch
 >>> [scipy-1.11.2] patching file scipy/spatial/setup.py
 >>> [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines).
 >>> [scipy-1.11.2] Applying ../patches/tests_no_internet_dependency.patch
 >>> [scipy-1.11.2] patching file scipy/datasets/meson.build
 >>> [scipy-1.11.2] 
 >>> [scipy-1.11.2] Host system:
 >>> [scipy-1.11.2] Darwin Helios.local 22.6.0 Darwin Kernel Version 
 >>> 22.6.0: Wed Jul  5 22:21:56 PDT 2023; 
 >>> root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64
 >>> [scipy-1.11.2] 
 >>> [scipy-1.11.2] C compiler: gcc
 >>> [scipy-1.11.2] C compiler version:
 >>> [scipy-1.11.2] Apple clang version 14.0.3 (clang-1403.0.22.14.1)
 >>> [scipy-1.11.2] Target: x86_64-apple-darwin22.6.0
 >>> [scipy-1.11.2] Thread model: posix
 >>> [scipy-1.11.2] InstalledDir: 
 >>> /Library/Developer/CommandLineTools/usr/bin
 >>> [scipy-1.11.2] 
 >>> [scipy-1.11.2] Package 'scipy' is currently not installed
 >>> [scipy-1.11.2] No legacy uninstaller found for 'scipy'; nothing to do
 >>> [scipy-1.11.2] Installing scipy-1.11.2
 >>> [scipy-1.11.2] DEPRECATION: --no-binary currently disables reading 
 >>> from the cache of locally built wheels. In the future --no-binary will 
 >>> not influence the wheel cache. pip 23.1 

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

[John Cremona]

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 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'
>> + printf '%s\n' 'no; skipping check'
>> + sage_spkg_install_meson-python=yes
>> ./configure: line 49870: sage_spkg_install_meson-python=yes: command not
>> found
>> + test yes = yes
>> + :
>> + sage_use_system_meson-python=no
>> ./configure: line 49874: sage_use_system_meson-python=no: command not
>> found
>> + test xno = xno
>> + :
>> + sage_use_system_meson_python=yes
>> + printf '%s\n' 'configure:49884: will use system package and not install
>> SPKG meson_python'
>> + printf '%s\n' 'configure: will use system package and not install SPKG
>> meson_python'
>> +
>>
>> On Sunday, September 17, 2023 at 1:34:35 PM UTC-7 Dima Pasechnik wrote:
>>
>>>
>>>
>>> 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" succeeds, as does "make".
>>>
>>> $ cat build/pkgs/scipy/dependencies
>>>  $(BLAS) gfortran numpy pybind11 cython pythran | $(PYTHON_TOOLCHAIN)
>>> meson_python $(PYTHON)
>>>
>>> looks OK. So this looks like a bug in our build system
>>>
>>>
>>> >
>>> >
>>> >
>>> > On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
>>> >>
>>> >> 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] 
>>> >>> [sagelib-10.2.beta3]   Removing file or directory
>>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
>>> >>> [sagelib-10.2.beta3]   Removing pth entries from
>>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
>>> >>> [sagelib-10.2.beta3]   Removing entry:
>>> /Users/kwankyu/GitHub/sage-dev/src
>>> >>> [sagelib-10.2.beta3]   Successfully uninstalled
>>> sagemath-standard-10.2b3
>>> >>> [sagelib-10.2.beta3]   Running setup.py develop for sagemath-standard
>>> >>> [sagelib-10.2.beta3] Running command python setup.py develop
>>> >>> [scipy-1.11.2] Setting up build directory for scipy-1.11.2
>>> >>> [scipy-1.11.2] Finished extraction
>>> >>> [scipy-1.11.2] Applying patches from ../patches...
>>> >>> [scipy-1.11.2] Applying ../patches/numpy-include.patch
>>> >>> [scipy-1.11.2] patching file scipy/spatial/setup.py
>>> >>> [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines).
>>> >>> [scipy-1.11.2] Applying ../patches/tests_no_internet_dependency.patch
>>> >>> [scipy-1.11.2] patching file scipy/datasets/meson.build
>>> >>> [scipy-1.11.2] 
>>> >>> [scipy-1.11.2] Host system:
>>> >>> [scipy-1.11.2] Darwin Helios.local 22.6.0 Darwin Kernel Version
>>> 22.6.0: Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64
>>> x86_64
>>> >>> [scipy-1.11.2] 
>>> >>> [scipy-1.11.2] C compiler: gcc
>>> >>> [scipy-1.11.2] C compiler version:
>>> >>> [scipy-1.11.2] Apple clang version 14.0.3 (clang-1403.0.22.14.1)
>>> >>> [scipy-1.11.2] Target: x86_64-apple-darwin22.6.0
>>> >>> [scipy-1.11.2] Thread model: posix
>>> >>> [scipy-1.11.2] InstalledDir:
>>> /Library/Developer/CommandLineTools/usr/bin
>>> >>> [scipy-1.11.2] 
>>> >>> [scipy-1.11.2] Package 'scipy' is currently not installed
>>> >>> [scipy-1.11.2] No legacy uninstaller found for 'scipy'; nothing to do
>>> >>> [scipy-1.11.2] Installing scipy-1.11.2
>>> >>> [scipy-1.11.2] DEPRECATION: --no-binary currently disables reading
>>> from the cache of locally built wheels. In the future --no-binary will not
>>> influence the wheel cache. pip 23.1 will enforce this behaviour change. A
>>> possible replacement is to use the --no-cache-dir option. You can use the
>>> flag --use-feature=no-binary-enable-wheel-cache to test the upcoming
>>> behaviour. Discussion can be found at
>>> https://github.com/pypa/pip/issues/11453
>>> >>> [scipy-1.11.2] Processing
>>> 

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

[Matthias Köppe]

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'
> + printf '%s\n' 'no; skipping check'
> + sage_spkg_install_meson-python=yes
> ./configure: line 49870: sage_spkg_install_meson-python=yes: command not 
> found
> + test yes = yes
> + :
> + sage_use_system_meson-python=no
> ./configure: line 49874: sage_use_system_meson-python=no: command not found
> + test xno = xno
> + :
> + sage_use_system_meson_python=yes
> + printf '%s\n' 'configure:49884: will use system package and not install 
> SPKG meson_python'
> + printf '%s\n' 'configure: will use system package and not install SPKG 
> meson_python'
> +
>
> On Sunday, September 17, 2023 at 1:34:35 PM UTC-7 Dima Pasechnik wrote:
>
>>
>>
>> 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" succeeds, as does "make".
>>
>> $ cat build/pkgs/scipy/dependencies
>>  $(BLAS) gfortran numpy pybind11 cython pythran | $(PYTHON_TOOLCHAIN) 
>> meson_python $(PYTHON)
>>
>> looks OK. So this looks like a bug in our build system 
>>
>>
>> >
>> >
>> >
>> > On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
>> >>
>> >> 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] 
>> >>> [sagelib-10.2.beta3]   Removing file or directory 
>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
>> >>> [sagelib-10.2.beta3]   Removing pth entries from 
>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
>> >>> [sagelib-10.2.beta3]   Removing entry: 
>> /Users/kwankyu/GitHub/sage-dev/src
>> >>> [sagelib-10.2.beta3]   Successfully uninstalled 
>> sagemath-standard-10.2b3
>> >>> [sagelib-10.2.beta3]   Running setup.py develop for sagemath-standard
>> >>> [sagelib-10.2.beta3] Running command python setup.py develop
>> >>> [scipy-1.11.2] Setting up build directory for scipy-1.11.2
>> >>> [scipy-1.11.2] Finished extraction
>> >>> [scipy-1.11.2] Applying patches from ../patches...
>> >>> [scipy-1.11.2] Applying ../patches/numpy-include.patch
>> >>> [scipy-1.11.2] patching file scipy/spatial/setup.py
>> >>> [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines).
>> >>> [scipy-1.11.2] Applying ../patches/tests_no_internet_dependency.patch
>> >>> [scipy-1.11.2] patching file scipy/datasets/meson.build
>> >>> [scipy-1.11.2] 
>> >>> [scipy-1.11.2] Host system:
>> >>> [scipy-1.11.2] Darwin Helios.local 22.6.0 Darwin Kernel Version 
>> 22.6.0: Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 
>> x86_64
>> >>> [scipy-1.11.2] 
>> >>> [scipy-1.11.2] C compiler: gcc
>> >>> [scipy-1.11.2] C compiler version:
>> >>> [scipy-1.11.2] Apple clang version 14.0.3 (clang-1403.0.22.14.1)
>> >>> [scipy-1.11.2] Target: x86_64-apple-darwin22.6.0
>> >>> [scipy-1.11.2] Thread model: posix
>> >>> [scipy-1.11.2] InstalledDir: 
>> /Library/Developer/CommandLineTools/usr/bin
>> >>> [scipy-1.11.2] 
>> >>> [scipy-1.11.2] Package 'scipy' is currently not installed
>> >>> [scipy-1.11.2] No legacy uninstaller found for 'scipy'; nothing to do
>> >>> [scipy-1.11.2] Installing scipy-1.11.2
>> >>> [scipy-1.11.2] DEPRECATION: --no-binary currently disables reading 
>> from the cache of locally built wheels. In the future --no-binary will not 
>> influence the wheel cache. pip 23.1 will enforce this behaviour change. A 
>> possible replacement is to use the --no-cache-dir option. You can use the 
>> flag --use-feature=no-binary-enable-wheel-cache to test the upcoming 
>> behaviour. Discussion can be found at 
>> https://github.com/pypa/pip/issues/11453
>> >>> [scipy-1.11.2] Processing 
>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/var/tmp/sage/build/scipy-1.11.2/src
>> >>> [scipy-1.11.2]   Preparing metadata (pyproject.toml): started
>> >>> [scipy-1.11.2]   Running command Preparing metadata (pyproject.toml)
>> >>> [scipy-1.11.2]   Preparing metadata (pyproject.toml): finished with 
>> status 'done'
>> >>> [scipy-1.11.2] ERROR: Exception:
>> 

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

[Matthias Köppe]

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 
found
+ test yes = yes
+ :
+ sage_use_system_meson-python=no
./configure: line 49874: sage_use_system_meson-python=no: command not found
+ test xno = xno
+ :
+ sage_use_system_meson_python=yes
+ printf '%s\n' 'configure:49884: will use system package and not install 
SPKG meson_python'
+ printf '%s\n' 'configure: will use system package and not install SPKG 
meson_python'
+

On Sunday, September 17, 2023 at 1:34:35 PM UTC-7 Dima Pasechnik wrote:

>
>
> 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" succeeds, as does "make".
>
> $ cat build/pkgs/scipy/dependencies
>  $(BLAS) gfortran numpy pybind11 cython pythran | $(PYTHON_TOOLCHAIN) 
> meson_python $(PYTHON)
>
> looks OK. So this looks like a bug in our build system 
>
>
> >
> >
> >
> > On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
> >>
> >> 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] 
> >>> [sagelib-10.2.beta3]   Removing file or directory 
> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
> >>> [sagelib-10.2.beta3]   Removing pth entries from 
> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
> >>> [sagelib-10.2.beta3]   Removing entry: 
> /Users/kwankyu/GitHub/sage-dev/src
> >>> [sagelib-10.2.beta3]   Successfully uninstalled 
> sagemath-standard-10.2b3
> >>> [sagelib-10.2.beta3]   Running setup.py develop for sagemath-standard
> >>> [sagelib-10.2.beta3] Running command python setup.py develop
> >>> [scipy-1.11.2] Setting up build directory for scipy-1.11.2
> >>> [scipy-1.11.2] Finished extraction
> >>> [scipy-1.11.2] Applying patches from ../patches...
> >>> [scipy-1.11.2] Applying ../patches/numpy-include.patch
> >>> [scipy-1.11.2] patching file scipy/spatial/setup.py
> >>> [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines).
> >>> [scipy-1.11.2] Applying ../patches/tests_no_internet_dependency.patch
> >>> [scipy-1.11.2] patching file scipy/datasets/meson.build
> >>> [scipy-1.11.2] 
> >>> [scipy-1.11.2] Host system:
> >>> [scipy-1.11.2] Darwin Helios.local 22.6.0 Darwin Kernel Version 
> 22.6.0: Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 
> x86_64
> >>> [scipy-1.11.2] 
> >>> [scipy-1.11.2] C compiler: gcc
> >>> [scipy-1.11.2] C compiler version:
> >>> [scipy-1.11.2] Apple clang version 14.0.3 (clang-1403.0.22.14.1)
> >>> [scipy-1.11.2] Target: x86_64-apple-darwin22.6.0
> >>> [scipy-1.11.2] Thread model: posix
> >>> [scipy-1.11.2] InstalledDir: 
> /Library/Developer/CommandLineTools/usr/bin
> >>> [scipy-1.11.2] 
> >>> [scipy-1.11.2] Package 'scipy' is currently not installed
> >>> [scipy-1.11.2] No legacy uninstaller found for 'scipy'; nothing to do
> >>> [scipy-1.11.2] Installing scipy-1.11.2
> >>> [scipy-1.11.2] DEPRECATION: --no-binary currently disables reading 
> from the cache of locally built wheels. In the future --no-binary will not 
> influence the wheel cache. pip 23.1 will enforce this behaviour change. A 
> possible replacement is to use the --no-cache-dir option. You can use the 
> flag --use-feature=no-binary-enable-wheel-cache to test the upcoming 
> behaviour. Discussion can be found at 
> https://github.com/pypa/pip/issues/11453
> >>> [scipy-1.11.2] Processing 
> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/var/tmp/sage/build/scipy-1.11.2/src
> >>> [scipy-1.11.2]   Preparing metadata (pyproject.toml): started
> >>> [scipy-1.11.2]   Running command Preparing metadata (pyproject.toml)
> >>> [scipy-1.11.2]   Preparing metadata (pyproject.toml): finished with 
> status 'done'
> >>> [scipy-1.11.2] ERROR: Exception:
> >>> [scipy-1.11.2] Traceback (most recent call last):
> >>> [scipy-1.11.2]   File 
> "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/cli/base_command.py",
>  
> line 160, in exc_logging_wrapper
> >>> 

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

[Dima Pasechnik]

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" succeeds, as does "make".

$ cat build/pkgs/scipy/dependencies
 $(BLAS) gfortran numpy pybind11 cython pythran | $(PYTHON_TOOLCHAIN)
meson_python $(PYTHON)

looks OK. So this looks like a bug in our build system

>
>
>
> On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
>>
>> 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] 
>>> [sagelib-10.2.beta3]   Removing file or directory
/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
>>> [sagelib-10.2.beta3]   Removing pth entries from
/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
>>> [sagelib-10.2.beta3]   Removing entry:
/Users/kwankyu/GitHub/sage-dev/src
>>> [sagelib-10.2.beta3]   Successfully uninstalled
sagemath-standard-10.2b3
>>> [sagelib-10.2.beta3]   Running setup.py develop for sagemath-standard
>>> [sagelib-10.2.beta3] Running command python setup.py develop
>>> [scipy-1.11.2] Setting up build directory for scipy-1.11.2
>>> [scipy-1.11.2] Finished extraction
>>> [scipy-1.11.2] Applying patches from ../patches...
>>> [scipy-1.11.2] Applying ../patches/numpy-include.patch
>>> [scipy-1.11.2] patching file scipy/spatial/setup.py
>>> [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines).
>>> [scipy-1.11.2] Applying ../patches/tests_no_internet_dependency.patch
>>> [scipy-1.11.2] patching file scipy/datasets/meson.build
>>> [scipy-1.11.2] 
>>> [scipy-1.11.2] Host system:
>>> [scipy-1.11.2] Darwin Helios.local 22.6.0 Darwin Kernel Version 22.6.0:
Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64
>>> [scipy-1.11.2] 
>>> [scipy-1.11.2] C compiler: gcc
>>> [scipy-1.11.2] C compiler version:
>>> [scipy-1.11.2] Apple clang version 14.0.3 (clang-1403.0.22.14.1)
>>> [scipy-1.11.2] Target: x86_64-apple-darwin22.6.0
>>> [scipy-1.11.2] Thread model: posix
>>> [scipy-1.11.2] InstalledDir: /Library/Developer/CommandLineTools/usr/bin
>>> [scipy-1.11.2] 
>>> [scipy-1.11.2] Package 'scipy' is currently not installed
>>> [scipy-1.11.2] No legacy uninstaller found for 'scipy'; nothing to do
>>> [scipy-1.11.2] Installing scipy-1.11.2
>>> [scipy-1.11.2] DEPRECATION: --no-binary currently disables reading from
the cache of locally built wheels. In the future --no-binary will not
influence the wheel cache. pip 23.1 will enforce this behaviour change. A
possible replacement is to use the --no-cache-dir option. You can use the
flag --use-feature=no-binary-enable-wheel-cache to test the upcoming
behaviour. Discussion can be found at
https://github.com/pypa/pip/issues/11453
>>> [scipy-1.11.2] Processing
/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/var/tmp/sage/build/scipy-1.11.2/src
>>> [scipy-1.11.2]   Preparing metadata (pyproject.toml): started
>>> [scipy-1.11.2]   Running command Preparing metadata (pyproject.toml)
>>> [scipy-1.11.2]   Preparing metadata (pyproject.toml): finished with
status 'done'
>>> [scipy-1.11.2] ERROR: Exception:
>>> [scipy-1.11.2] Traceback (most recent call last):
>>> [scipy-1.11.2]   File
"/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/cli/base_command.py",
line 160, in exc_logging_wrapper
>>> [scipy-1.11.2] status = run_func(*args)
>>> [scipy-1.11.2]   File
"/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/cli/req_command.py",
line 247, in wrapper
>>> [scipy-1.11.2] return func(self, options, args)
>>> [scipy-1.11.2]   File
"/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/commands/wheel.py",
line 170, in run
>>> [scipy-1.11.2] requirement_set = resolver.resolve(reqs,
check_supported_wheels=True)
>>> [scipy-1.11.2]   File
"/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/resolver.py",
line 73, in resolve
>>> [scipy-1.11.2] collected =
self.factory.collect_root_requirements(root_reqs)
>>> [scipy-1.11.2]   File