Sage 9.1.rc1 released

[Volker Braun]

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 

Due to the blocker ticket bonanza we aren't stabilizing yet, so expect more rc versions...

249fc90389 (tag: 9.1.rc1, trac/develop) Updated SageMath version to 9.1.rc1

358caa9bcc Trac #29546: Upgrade: OpenSSL 1.1.1g

4328c62924 Trac #29501: spkg-check.in: Do not use sdh_make to do 'make check', to avoid misleading messages

9ad1188c15 Trac #29510: spkg-check.in: Remove messages that duplicate sage-spkg's messages

f00937e20c Trac #29489: Fix configure messages "rm: conftest.dir: is a directory"

cf92498b12 Trac #29525: SSTPosets are lattices

bc4b0ec1f9 Trac #29524: bug with rational input in IntegerVectors

0feabfd714 Trac #29508: Add system package lists for pandoc (prereq of rst2ipynb)

9fe26c1d01 Trac #29442: Fix failing doctest in src/sage/interfaces/tachyon.py

447faa145a Trac #29424: Slackware: system packages fix

655d6b8395 Trac #29392: ./configure --enable-experimental-packages --enable-download-from-upstream-url

1fc05087b8 Trac #29065: Inverse function for `gale_transform`

aa09eef5f3 Trac #28866: doctest killed due to abort in geometry/polyhedron/base.py

98c7ce0824 Trac #29532: cygwin: Fix spkg-configure.m4 for iconv

9980a1fa1d Trac #29518: remove deprecated stuff from graphs

1007d3cccd Trac #29417: tox.ini, GitHub CI workflow - minor fixes, more homebrew configuration factors, improve docker interface

5d8fcd0929 Trac #29324: Translation with both Vrep and Hrep

08777b75f4 Trac #21262: Center related classes and methods in Skew Polynomials

4ad646eba7 Trac #19677: Document the output type of Graph.matching(value_only=True)

9529870fdb Trac #29526: eclib spkg-configure.m4: Check for mwrank executable

0a8d939ab3 Trac #29477: Fix enumeration alignment in doc of RealField

5e123ca270 Trac #29513: sage-spkg: Remove check for executable permission on spkg-install.in script templates

6668539ab3 Trac #29492: Remove outdated boilerplate from spkg-install.in and spkg-check.in

9a87bf3e07 Trac #29435: some details as suggested by pyflakes

8fc13d0382 Trac #29407: Fix a bug in residue_field and add get_place to rational function fields

082626e207 Trac #29108: Cleanup schemes/readme.py

2ee8e1490f Trac #29517: register_as_coercion fails when no coercion map was already discovered

19947d7b42 Trac #29197: mcqd  needs an update of spkg-install

9af553f1c9 Trac #28971: tachyon syntax error when building doc

a64c5b87e2 Trac #28173: Implemented Is_Newton for Dynamical Systems

4ab89e9600 Trac #29505: add missing raise and fix some imports in number fields

46a4440b66 Trac #29503: allow custom prefix in shuffle and Zinbiel algebras

f5db28573c Trac #29494: Reject old system pari with bug in hyperellcharpoly

5408226897 Trac #29491: gp2c spkg-configure.m4 cleanup

e903b7191f Trac #29487: debian: Add system package providing the executable sqlite3

b907f22b62 Trac #29482: Fix assorted documentation errors in TESTS blocks and underscore methods

ed5533ff0c Trac #29453: Detect and use the system fflas-ffpack

c68ef6d5bc Trac #29444: Upgrade matplotlib to 2.2.5 (last release supporting py2)

8f83955ac9 Trac #29385: Fix the alignment of the numbered points in finite-dimensional algebras with basis

816722b347 Trac #29384: Clean up src/bin/sage-env-config.in: Move logic to src/bin/sage-env, move non-environment configuration variables to sage_conf.py

6403c3cef3 Trac #29054: polymake: Add system package lists for Perl prereqs

d0eb939577 Trac #28915: Upgrade: OpenSSL 1.1.1f

12367fdb68 Trac #28868: 7 imagemagick failing doctest in plot/animate.py

0af715d7d1 Trac #27272: spkg-configure.m4 for iml

a4c2125590 Trac #25796: Implement elementary cellular automata

47960151f1 Trac #29504: ./configure + homebrew: recommend the script .homebrew-build-env

0779c8c2a5 Trac #29496: Update README.md and Installation Guide

2713a7b0a1 Trac #29488: sage-spkg: Advertise sage -buildsh, not sage -sh

e7a37fd885 Trac #29473: fedora: Add python3-devel system packages, standardize build/pkgs/python3/distros/*.txt, fix cysignals build on fedora

bf8c781799 Trac #29404: Fix build failures of pynac on macos with system python3

5d535e55b5 Trac #26018: Race conditions because of DESTDIR

caf525de1d Trac #29460: Run configure less often

b42af5e1f9 Trac #29408: Fix build errors with pplpy, scipy, kiwisolver, fpylll on macos with system python3

58c92b8269 Trac #29481: Fix up "sage -i" for optional packages

10ed24e3ed (tag: 9.1.rc0) Updated SageMath version to 9.1.rc0

[Matthias Köppe]

On Wednesday, April 22, 2020 at 3:41:50 PM UTC-7, Volker Braun wrote:

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 

Due to the blocker ticket bonanza we aren't stabilizing yet, so expect more rc versions...

249fc90389 (tag: 9.1.rc1, trac/develop) Updated SageMath version to 9.1.rc1

Tests 

- for Linux and macOS run at https://github.com/mkoeppe/sage/actions/runs/85334061

- for optional packages at https://github.com/mkoeppe/sage/actions/runs/85334059

- for Cygwin at https://github.com/mkoeppe/sage/actions/runs/85334058

[Samuel Lelievre]

> Date: Wed 2020-04-22 22:41:50 UTC
> From: Volker Braun

> Subject: Sage 9.1.rc1 released

Thanks for this new development release.

On macOS 10.14.6 Mojave with lots of Homebrew

packages installed, failed to build Pillow. Logs:

https://www.math.u-psud.fr/~lelievre/t/sage3logs.zip

[Dima Pasechnik]

What Python3 it is with?

Could you check whether the pillow problem is related to #29019  ?

there are there links to Pillow bug tracker...

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/90d822a1-46bf-4642-b4af-29dd84502729%40googlegroups.com.

[Frédéric Chapoton]

First build failure on my laptop since a very long time:

Checking whether SageMath should install SPKG gp2c...

configure: gp2c has already been installed by SageMath

configure: gp prefix is .

configure: error: unable to locate pari.cfg

If you would like to try to build Sage anyway (to help porting),

export the variable 'SAGE_PORT' to something non-empty.

make[1]: *** [Makefile:49: build/make/Makefile] Error 1

make[1] : on quitte le répertoire « /home/chapoton/sage3 »

make: *** [Makefile:32: base-toolchain] Error 2

I would hate to be forced to "make dist-clean".

[Dima Pasechnik]

On Thu, 23 Apr 2020, 15:19 Frédéric Chapoton, <fchap...@gmail.com> wrote:

First build failure on my laptop since a very long time:

Checking whether SageMath should install SPKG gp2c...

configure: gp2c has already been installed by SageMath

configure: gp prefix is .

configure: error: unable to locate pari.cfg

If you would like to try to build Sage anyway (to help porting),

export the variable 'SAGE_PORT' to something non-empty.

make[1]: *** [Makefile:49: build/make/Makefile] Error 1

make[1] : on quitte le répertoire « /home/chapoton/sage3 »

make: *** [Makefile:32: base-toolchain] Error 2

you can remove build/pkgs/gp2c/spkg-configure.m4

and then

./bootstrap && ./configure && make build

this is of course a hack...

--
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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/dfd62bdf-7e70-4456-a845-e0dee8c96ee3%40googlegroups.com.

[Frédéric Chapoton]

Thanks a lot. This worked. Will this trick need to be repeated ?

Frederic

To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.

[Dima Pasechnik]

On Thu, 23 Apr 2020, 16:08 Frédéric Chapoton, <fchap...@gmail.com> wrote:

Thanks a lot. This worked. Will this trick need to be repeated ?

it is hard to tell. It is impossible to make progress on configure while making sure that it all the time updates without distclean for everyone.

To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/d13c04a9-54f6-4993-8629-bd3e673136f2%40googlegroups.com.

[kcrisman]

Built from scratch on OS X 10.11.6, using ./configure and then make.  I suggest that https://doc.sagemath.org/html/en/installation/source.html is incorrect in suggesting that Py3 is necessary to *build* Sage.

Testing that Sage starts...

[2020-04-23 12:33:27] SageMath version 9.1.rc1, Release Date: 2020-04-22

Yes, Sage starts.

real 250m34.371s

user 483m50.050s

sys 96m20.518s

Sage build/upgrade complete!

$ python --version

Python 2.7.10

[Matthias Köppe]

On Thursday, April 23, 2020 at 9:50:49 AM UTC-7, kcrisman wrote:

Built from scratch on OS X 10.11.6, using ./configure and then make.  I suggest that https://doc.sagemath.org/html/en/installation/source.html is incorrect in suggesting that Py3 is necessary to *build* Sage.

You're right, this needs to be updated. Python 2 also works. I've opened https://trac.sagemath.org/ticket/29556 for updating the installation instructions.

[kcrisman]

Built from scratch on OS X 10.11.6, using ./configure and then make.  I suggest that https://doc.sagemath.org/html/en/installation/source.html is incorrect in suggesting that Py3 is necessary to *build* Sage.

You're right, this needs to be updated. Python 2 also works. I've opened https://trac.sagemath.org/ticket/29556 for updating the installation instructions.

Great.  By the way, passes all (basic) tests, four files needed to be rerun for timing out :-) 

[kcrisman]

And to be clear, this was the default setup - I didn't try to use Py2 for Sage itself:

$ ./sage -ipython

Python 3.7.3 (default, Apr 23 2020, 09:19:49)  

[Matthias Köppe]

On Wednesday, April 22, 2020 at 11:55:21 PM UTC-7, Samuel Lelievre wrote:

On macOS 10.14.6 Mojave with lots of Homebrew

packages installed, failed to build Pillow. Logs:

https://www.math.u-psud.fr/~lelievre/t/sage3logs.zip

Looking at the logs, I guess that this might be caused by the homebrew package "libzip".

 

[Matthias Köppe]

This is now https://trac.sagemath.org/ticket/29562, needs review 

[Matthias Köppe]

On Wednesday, April 22, 2020 at 3:41:50 PM UTC-7, Volker Braun wrote:

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 

Due to the blocker ticket bonanza we aren't stabilizing yet, so expect more rc versions...

249fc90389 (tag: 9.1.rc1, trac/develop) Updated SageMath version to 9.1.rc1

Tests on macOS from https://github.com/mkoeppe/sage/actions/runs/85931516:

homebrew-macos-python2, standard (https://github.com/mkoeppe/sage/runs/612692798)

sage -t src/sage/categories/finite_semigroups.py  # 1 doctest failed

sage -t src/sage/combinat/cluster_algebra_quiver/cluster_seed.py  # 5 doctests failed

sage -t src/sage/combinat/finite_state_machine.py  # 3 doctests failed

sage -t src/sage/combinat/root_system/integrable_representations.py  # 1 doctest failed

sage -t src/sage/doctest/util.py  # 4 doctests failed

sage -t src/sage/graphs/base/c_graph.pyx  # 1 doctest failed

sage -t src/sage/graphs/generic_graph.py  # 5 doctests failed

sage -t src/sage/graphs/graph_decompositions/vertex_separation.pyx  # 1 doctest failed

sage -t src/sage/graphs/traversals.pyx  # 4 doctests failed

sage -t src/sage/graphs/graph.py  # 1 doctest failed

sage -t src/sage/graphs/path_enumeration.pyx  # 1 doctest failed

sage -t src/sage/groups/perm_gps/symgp_conjugacy_class.py  # 1 doctest failed

sage -t src/sage/groups/perm_gps/permgroup.py  # 1 doctest failed

sage -t src/sage/dynamics/arithmetic_dynamics/projective_ds.py  # Timed out

sage -t src/sage/matroids/constructor.py  # 1 doctest failed

sage -t src/sage/matroids/minor_matroid.py  # 1 doctest failed

sage -t src/sage/misc/sage_input.py  # 1 doctest failed

sage -t src/sage/manifolds/differentiable/tensorfield.py  # Timed out

sage -t src/sage/numerical/backends/logging_backend.py  # 4 doctests failed

sage -t src/sage/numerical/interactive_simplex_method.py  # 1 doctest failed

sage -t src/sage/plot/plot3d/base.pyx  # Timed out

sage -t src/sage/plot/plot3d/implicit_plot3d.py  # Timed out

sage -t src/sage/repl/ipython_kernel/widgets_sagenb.py  # 2 doctests failed

sage -t src/sage/plot/plot3d/parametric_plot3d.py  # Timed out

sage -t src/sage/plot/plot3d/plot3d.py  # Timed out

sage -t src/sage/plot/plot3d/shapes2.py  # Timed out

sage -t src/sage/rings/polynomial/multi_polynomial_ideal.py  # 11 doctests failed

sage -t src/sage/sets/recursively_enumerated_set.pyx  # 2 doctests failed

sage -t src/sage/tests/books/computational-mathematics-with-sagemath/mpoly_doctest.py  # 5 doctests failed

sage -t src/sage/tests/books/computational-mathematics-with-sagemath/sol/mpoly_doctest.py  # 3 doctests failed

sage -t src/sage/schemes/elliptic_curves/ell_number_field.py  # Timed out

Many of these seem to come from an unexpected sorting order in printing dictionaries, like this one:

File "src/sage/tests/books/computational-mathematics-with-sagemath/mpoly_doctest.py", line 112, in sage.tests.books.computational-mathematics-with-sagemath.mpoly_doctest

Failed example:

    J.variety() # py2

Expected:

    [{y: 2, z: 1, x: 3}]

Got:

    [{x: 3, z: 1, y: 2}]

This seems to be specific to this platform; python2 tests on Linux do not have this problem.

homebrew-macos-python3_pythonorg, minimal (https://github.com/mkoeppe/sage/runs/612692911), 

homebrew-macos-python3_xcode, standard (https://github.com/mkoeppe/sage/runs/612692857), 

and other tests with python3 have one consistent doctest failure:

File "src/sage/interfaces/gap.py", line 485, in sage.interfaces.gap.Gap_generic._read_in_file_command

Failed example:

    gap.read(filename)

Exception raised:

    Traceback (most recent call last):

      File "/Users/runner/runners/2.169.1/work/sage/sage/.tox/local-homebrew-macos-python3_pythonorg-minimal/local/lib/python3.7/site-packages/sage/interfaces/gap.py", line 768, in _eval_line

        raise RuntimeError("%s produced error output\n%s\n   executing %s"%(self, error,line))

    RuntimeError: Gap produced error output

    Error, Function call: <func> must return a value

       executing Read("/Users/runner/runners/2.169.1/work/sage/sage/.tox/local-homebrew-macos-python3_pythonorg-minimal/.sage/temp/Mac-1762.local/29176/interface/tmp29179");

    During handling of the above exception, another exception occurred:

conda-forge-macos, minimal (https://github.com/mkoeppe/sage/runs/612692956) has a number of doctest failures due to warnings emitted during Cython runs, like the following:

File "src/sage/graphs/connectivity.pyx", line 2671, in sage.graphs.connectivity._Component.__init__

Failed example:

    cython(os.linesep.join(cython_code))

Expected:

    Polygon: 2 3 4

Got:

    ld: warning: -pie being ignored. It is only used when linking a main executable

    Polygon: 2 3 4

If anyone is interested in these failures, please open Trac tickets.

[Justin C. Walker]

> On Apr 22, 2020, at 15:41 , Volker Braun <vbrau...@gmail.com> wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html

Built from fresh clones of the develop branch, on three different macOS systems: 10.13.6 (2017 iMac Pro, 18-core Xeon W), 10.14.6 (2017 MBP Quad-core Core i7), 10.15.4 (2019 MBP, 9-core Core i9).

No build problems, and all tests (‘ptestlong’) passed on all systems!

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Absorption of Federal Funds
--------
Men are from Earth.
Women are from Earth.
Deal with it.
--------

[Sébastien Labbé]

Testing few optional and external packages, here is what I get:

Using --optional=4ti2,cbc,ccache,cryptominisat,dot2tex,e_antic,external,glucose,latte_int,lidia,lrslib,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin,sage_numerical_backends_cplex,sage_numerical_backends_gurobi

----------------------------------------------------------------------
sage -t --long src/sage/databases/findstat.py  # 8 doctests failed
sage -t --long src/sage/databases/oeis.py  # 1 doctest failed
sage -t --long src/sage/geometry/polyhedron/base.py  # Bad exit: 1
sage -t --long src/sage/graphs/generators/smallgraphs.py  # 2 doctests failed
sage -t --long src/sage/symbolic/integration/external.py  # 1 doctest failed
----------------------------------------------------------------------
External software detected for doctesting: cplex,ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc

Rerunning failed doctests, I get the same.

The external and oeis failures are copied below.

Follow up at https://trac.sagemath.org/ticket/25536

sage -t --long src/sage/symbolic/integration/external.py
**********************************************************************
File "src/sage/symbolic/integration/external.py", line 91, in sage.symbolic.integration.external.mma_free_integrator
Failed example:
    integral(sin(y)^2, y, algorithm='mathematica_free') # optional - internet
Expected:
    1/2*y - 1/4*sin(2*y)
Got:
    -1/2*cos(y)*sin(y) + 1/2*y
**********************************************************************
1 item had failures:
   1 of   7 in sage.symbolic.integration.external.mma_free_integrator
    8 fricas tests not run
    0 tests not run because we ran out of time
    [36 tests, 1 failure, 20.70 s]


   
sage -t --long src/sage/databases/oeis.py
**********************************************************************
File "src/sage/databases/oeis.py", line 489, in sage.databases.oeis.OEIS.find_by_description
Failed example:
    oeis('beaver', max_results=4, first_result=2)     # optional -- internet
Expected:
    0: A131956: Busy Beaver variation: maximum number of steps for ...
    1: A141475: Number of Turing machines with n states following ...
    2: A131957: Busy Beaver sigma variation: maximum number of 1's ...
    3: A052200: Number of n-state, 2-symbol, d+ in {LEFT, RIGHT}, ...
Got:
    0: A131956: Busy Beaver variation: maximum number of steps for a 2-state, 2-symbol Turing machine running on a tape which is initialized with the number n in binary and 0's everywhere else. The machine is started at the rightmost bit in the number n.
    1: A141475: Number of Turing machines with n states following the standard formalism of the busy beaver problem where the head of a Turing machine either moves to the right or to the left, but none once halted.
    2: A131957: Busy Beaver sigma variation: maximum number of 1's on the final tape, for a 2-state, 2-symbol Turing machine running on a tape which is initialized with the number n in binary and 0's everywhere else. The machine is started at the rightmost bit in the number n.
    3: A333479: Busy Beaver for binary lambda calculus: the maximum normal form size of any closed lambda term of size n, or 0 if no closed term of size n exists.
**********************************************************************
1 item had failures:
   1 of   5 in sage.databases.oeis.OEIS.find_by_description
    5 webbrowser tests not run
    0 tests not run because we ran out of time
    [281 tests, 1 failure, 29.41 s]

[kcrisman]

The external and oeis failures are copied below.

Follow up at https://trac.sagemath.org/ticket/25536

I've added tickets for them, and to the list there.  Both should be pretty trivial to fix - unfortunately I just deleted my 9.1rc install to save disk space.

[Samuel Lelièvre]

Thu 2020-04-23 à 09:09, Dima Pasechnik:
>
> On Thu, 23 Apr 2020, 14:55 Samuel Lelievre:
>>
>> > Subject: Sage 9.1.rc1 released

>>
>> On macOS 10.14.6 Mojave with lots of Homebrew
>> packages installed, failed to build Pillow. Logs:
>>
>> https://www.math.u-psud.fr/~lelievre/t/sage3logs.zip
>
> What Python3 it is with?
> Could you check whether the pillow problem is related to #29019?

> There are there links to Pillow bug tracker...

Thanks Dima for the excellent pointers once more.

The discussion at

https://trac.sagemath.org/ticket/29019

indeed had a link to

https://github.com/python-pillow/Pillow/issues/3438

with tricks related to

macOS_SDK_headers_for_macOS_10.14.pkg

I went for a serious spring cleaning, uninstalled
Apple's "Command-Line Tools for Developers" and
reinstalled them as well as the headers, uninstalled
and reinstalled Homebrew and MacTeX. Now more
up-to-date and with less accumulated cruft around.

With that, the build of SageMath 9.1.rc1 completed.

```
$ source ./.homebrew-build-env
$ make configure
[...]
$ CC=clang CXX=clang++ FC=gfortran \
OBJC=clang OBJCXX=clang++
./configure
[...]
$ make -s V=0
[...]
Sage build/upgrade complete!
```

And I can now happily use Sage 9.1.rc1 based on Python 3.7.7.

```
$ ./sage

SageMath version 9.1.rc1, Release Date: 2020-04-22

Using Python 3.7.7. Type "help()" for help.
Warning: this is a prerelease version, and it may be unstable.
sage:
```

Everything seems fine with tests:

```
$ make ptestlong

[...]

----------------------------------------------------------------------
All tests passed!
----------------------------------------------------------------------
Total time for all tests: 9656.0 seconds
cpu time: 23962.4 seconds
cumulative wall time: 37234.1 seconds
```

A few things maybe worth reporting.

1. The 'configure' step suggested to run

$ brew install ppl

even though I already had Homebrew's ppl. Intrigued,
I took a look at the part of 'config.log' checking ppl:

```
## ---------------------------------------------------- ##
## Checking whether SageMath should install SPKG ppl... ##
## ---------------------------------------------------- ##
configure:27878: checking whether any of glpk gmp mpir
is installed as or will be installed as SPKG
configure:27882: result: yes; install ppl as well
configure:28277: no suitable system package found for SPKG ppl
```

Since at least one of (glpk, gmp, mpir) either
was or would be installed as an SPKG, the script
concluded ppl should be installed as an SPKG too.

So the decision to install ppl was based on that,
not on the absence of ppl. In such a case, maybe
the script should not recommend installing ppl
(at least not without checking if it is there).

2. During `make ptestlong`, on three occasions
an alert that "Python quit unexpectedly" popped
up and offered to either (a) Ignore, (b) Inspect,
(c) Report to Apple (or something like that).

Does this happen because some doctests crash
Python on purpose and, because of now using
Homebrew's Python instead of building Sage's
own, this is now caught by macOS which offers
to report the crash to Apple?

[Matthias Köppe]

On Saturday, April 25, 2020 at 9:02:42 AM UTC-7, Samuel Lelievre wrote:

1. The 'configure' step suggested to run

  $ brew install ppl

even though I already had Homebrew's ppl. Intrigued,
I took a look at the part of 'config.log' checking ppl:

```
## ---------------------------------------------------- ##
## Checking whether SageMath should install SPKG ppl... ##
## ---------------------------------------------------- ##
configure:27878: checking whether any of glpk gmp mpir
is installed as or will be installed as SPKG
configure:27882: result: yes; install ppl as well
configure:28277: no suitable system package found for SPKG ppl
```

Since at least one of (glpk, gmp, mpir) either
was or would be installed as an SPKG, the script
concluded ppl should be installed as an SPKG too.

So the decision to install ppl was based on that,
not on the absence of ppl. In such a case, maybe
the script should not recommend installing ppl
(at least not without checking if it is there).

I collect wishlist items for this code at https://trac.sagemath.org/ticket/29146

("Meta-ticket: Refactor system package related scripts, tox.ini, build/bin/write_dockerfile.sh")

You can add your suggestion there. Won't happen for 9.1.

[Matthias Köppe]

On Saturday, April 25, 2020 at 9:02:42 AM UTC-7, Samuel Lelievre wrote:

```
$ source ./.homebrew-build-env

By the way, that script is fixed for the next rc in https://trac.sagemath.org/ticket/29562

 

$ make configure
[...]
$ CC=clang CXX=clang++ FC=gfortran \
  OBJC=clang OBJCXX=clang++
  ./configure
[...]

 

2. During `make ptestlong`, on three occasions

an alert that "Python quit unexpectedly" popped
up and offered to either (a) Ignore, (b) Inspect,
(c) Report to Apple (or something like that).

Does this happen because some doctests crash
Python on purpose and, because of now using
Homebrew's Python instead of building Sage's
own, this is now caught by macOS which offers
to report the crash to Apple?

We observed that too on https://trac.sagemath.org/ticket/29463

but have not investigated from which doctests this comes exactly.

[Samuel Lelievre]

Le samedi 25 avril 2020 18:15:55 UTC+2, Matthias Köppe a écrit :

On Saturday, April 25, 2020 at 9:02:42 AM UTC-7, Samuel Lelievre wrote:

1. The 'configure' step suggested to `brew install ppl`
even though I already had Homebrew's ppl. [...]

So the decision to install ppl was based on that,
not on the absence of ppl. In such a case, maybe
the script should not recommend installing ppl
(at least not without checking if it is there).

I collect wishlist items for this code at https://trac.sagemath.org/ticket/29146

("Meta-ticket: Refactor system package related scripts, tox.ini, build/bin/write_dockerfile.sh")

You can add your suggestion there. Won't happen for 9.1.

Opened

- Sage Trac ticket #29586

  Improve configure's recommendations

  https://trac.sagemath.org/ticket/29586

with milestone 9.2 and was adding it to #29146

but you beat me to it.