Re: [sage-release] Sage 9.2.beta12 released

with https://trac.sagemath.org/ticket/30536 , I can compile and start sage, and all tests pass `make -j1 testlong`. Le mercredi 9 septembre 2020 à 17:41:42 UTC+2, matthia...@gmail.com a écrit : > On Wednesday, September 9, 2020 at 8:35:10 AM

Re: [sage-release] Sage 9.2.beta12 released

On Wed, Sep 9, 2020 at 11:17 PM Matthias Köppe wrote: > > On Wednesday, September 9, 2020 at 3:08:31 PM UTC-7, Dima Pasechnik wrote: >> >> >> except that on macOS+Homebrew the latter wants the PATH like this: >> >> % cat ~/.zshrc >> >> export PATH="/usr/local/opt/python@3.7/bin:$PATH" >> >> I am

Re: [sage-release] Sage 9.2.beta12 released

On Wednesday, September 9, 2020 at 3:08:31 PM UTC-7, Dima Pasechnik wrote: > > > except that on macOS+Homebrew the latter wants the PATH like this: > > % cat ~/.zshrc > export PATH="/usr/local/opt/python@3.7/bin:$PATH" > > I am not sure whether putting /usr/local/bin first won't break Homebrew. >

Re: [sage-release] Sage 9.2.beta12 released

On Wed, Sep 9, 2020 at 11:00 PM Matthias Köppe wrote: > On Wednesday, September 9, 2020 at 2:23:36 PM UTC-7, Dima Pasechnik wrote: >> >> The autoconf macro in question is looping over the entries in the PATH >> (and this is documented behaviour) >> So the outer loop is >> >> for as_dir in $PATH

Re: [sage-release] Sage 9.2.beta12 released

On Wednesday, September 9, 2020 at 2:23:36 PM UTC-7, Dima Pasechnik wrote: > > The autoconf macro in question is looping over the entries in the PATH > (and this is documented behaviour) > So the outer loop is > > for as_dir in $PATH > > now, the PATH is a bit funny in my case: > > >

Re: [sage-release] Sage 9.2.beta12 released

On Wed, Sep 9, 2020 at 9:31 PM Matthias Köppe wrote: > Very strange, can you run it with ./configure CONFIG_SHELL="bash -x" and > post the output? > I think I know what's going on. The autoconf macro in question is looping over the entries in the PATH (and this is documented behaviour) So the

Re: [sage-release] Sage 9.2.beta12 released

Very strange, can you run it with ./configure CONFIG_SHELL="bash -x" and post the output? On Wednesday, September 9, 2020 at 1:17:04 PM UTC-7, Dima Pasechnik wrote: > > > > On Wed, Sep 9, 2020 at 9:04 PM Matthias Köppe > wrote: > > > > Are you using a configure cache? Because according to your

Re: [sage-release] Sage 9.2.beta12 released

On Wed, Sep 9, 2020 at 9:04 PM Matthias Köppe wrote: > > Are you using a configure cache? Because according to your config.log, it's only checking 1 binary I'm merely running CC=clang CXX=clang++ ./configure --enable-download-from-upstream-url after I reverted ---

Re: [sage-release] Sage 9.2.beta12 released

Are you using a configure cache? Because according to your config.log, it's only checking 1 binary On Wednesday, September 9, 2020 at 12:58:26 PM UTC-7, Dima Pasechnik wrote: > > On Wed, Sep 9, 2020 at 8:54 PM Matthias Köppe > wrote: > > > > Is "python3.8" in PATH? > of course. > >

Re: [sage-release] Sage 9.2.beta12 released

On Wed, Sep 9, 2020 at 8:54 PM Matthias Köppe wrote: > > Is "python3.8" in PATH? of course. dima@oucl13243 sagetrac-mirror % python3 Python 3.7.8 (default, Jul 8 2020, 14:18:28) [Clang 11.0.3 (clang-1103.0.32.62)] on darwin Type "help", "copyright", "credits" or "license" for more information.

Re: [sage-release] Sage 9.2.beta12 released

Is "python3.8" in PATH? On Wednesday, September 9, 2020 at 12:44:50 PM UTC-7, Dima Pasechnik wrote: > > here it is. The account shell is zsh, but this most probably does not > matter. > > On Wed, Sep 9, 2020 at 6:31 PM Matthias Köppe > wrote: > > > > On Wednesday, September 9, 2020 at

[sage-release] Re: Sage 9.2.beta12 released

On Tuesday, September 8, 2020 at 9:23:04 PM UTC-7, Matthias Köppe wrote: > > conda-forge-macos-standard ( > https://github.com/sagemath/sage/runs/1078909711): > [sagelib-9.2.beta12] > >

Re: [sage-release] Sage 9.2.beta12 released

On Wednesday, September 9, 2020 at 10:11:14 AM UTC-7, Dima Pasechnik wrote: > > by the way, I am not able to pick up Homebrew's python3.8 in the presence > of python3.7, unless I modify python3's spkg-configure.m4 to exclude > python3.7 and python3 from the list of Pythons it checks for. > >> >>

Re: [sage-release] Sage 9.2.beta12 released

by the way, I am not able to pick up Homebrew's python3.8 in the presence of python3.7, unless I modify python3's spkg-configure.m4 to exclude python3.7 and python3 from the list of Pythons it checks for. (on linux this seems to work well, so perhaps it is a macOS-only bug) On Wed, 9 Sep 2020,

Re: [sage-release] Sage 9.2.beta12 released

On Wednesday, September 9, 2020 at 8:35:10 AM UTC-7, David Coudert wrote: > > The traces of fortran 9 (and actually gcc 9) are due > to .homebrew-build-env. which contains: > > for l in "gcc@9/lib/gcc/9"; do > if [ -d "$HOMEBREW/opt/$l" ]; then >

Re: [sage-release] Sage 9.2.beta12 released

The traces of fortran 9 (and actually gcc 9) are due to .homebrew-build-env. which contains: for l in "gcc@9/lib/gcc/9"; do if [ -d "$HOMEBREW/opt/$l" ]; then LIBRARY_PATH="$HOMEBREW/opt/$l:$LIBRARY_PATH" fi done > Le 9 sept. 2020 à 17:01, Dima Pasechnik a écrit : > > ok,

Re: [sage-release] Sage 9.2.beta12 released

ok, you have a non-standard arb in your Homebrew install. you need to reinstall it, or perhaps better just remove it. you also have traces of gfortran 9 in LIBRARY_PATH - investigate and clean... On Wed, 9 Sep 2020, 15:57 david@gmail.com, wrote: > I can try to install ntl and flint, but

Re: [sage-release] Sage 9.2.beta12 released

I can try to install ntl and flint, but then I have to remove dependencies as well, right ? sapristi:sage dcoudert$ brew uninstall ntl flint Error: Refusing to uninstall /usr/local/Cellar/flint/2.6.3 because it is required by arb, which is currently installed. You can override this and force

Re: [sage-release] Sage 9.2.beta12 released

On Wednesday, September 9, 2020 at 2:49:19 AM UTC-7, david@gmail.com wrote: > > If I understand well, I’m facing the case (not completely sure): > homebrew-macos-python3_xcode-gcc_spkg-{minimal,standard}: Various build > errors (ignore for Sage 9.2) > > That is: macOS 10.15.6 with clang

Re: [sage-release] Sage 9.2.beta12 released

do you by any chance have g++ and/or gcc being "real" gcc, not just links to Apple's clang(++) ? E.g. I have % g++ -v Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1 Apple clang

Re: [sage-release] Sage 9.2.beta12 released

you do $ source .homebrew-build-env before builds, right? Post the top-level config.log On Wed, Sep 9, 2020 at 11:53 AM David Coudert wrote: > > > > Le 9 sept. 2020 à 12:04, Dima Pasechnik a écrit : > > On Wed, Sep 9, 2020 at 10:49 AM David Coudert wrote: > > > If I understand well, I’m

Re: [sage-release] Sage 9.2.beta12 released

> Le 9 sept. 2020 à 12:04, Dima Pasechnik a écrit : > > On Wed, Sep 9, 2020 at 10:49 AM David Coudert > wrote: >> >> If I understand well, I’m facing the case (not completely sure): >> homebrew-macos-python3_xcode-gcc_spkg-{minimal,standard}: Various build >>

Re: [sage-release] Sage 9.2.beta12 released

On Wed, Sep 9, 2020 at 10:49 AM David Coudert wrote: > > If I understand well, I’m facing the case (not completely sure): > homebrew-macos-python3_xcode-gcc_spkg-{minimal,standard}: Various build > errors (ignore for Sage 9.2) no, this is for macOS 11, still in beta, and not going to be

Re: [sage-release] Sage 9.2.beta12 released

If I understand well, I’m facing the case (not completely sure): homebrew-macos-python3_xcode-gcc_spkg-{minimal,standard}: Various build errors (ignore for Sage 9.2) That is: macOS 10.15.6 with clang version 11.0.3 (clang-1103.0.32.62) and all recommended packages installed with homebrew, and