[sage-devel] Re: OS X Big Sur progress report

2020-11-17 Thread John H Palmieri
You can probably eliminate some of the doctest errors with the following hack, which may not be the right way to proceed, but at least for me it allows doctesting to complete. Some of your other errors may be caused by using Python 3.9, and people are working on fixing those. diff --git a/src/s

[sage-devel] Re: OS X Big Sur progress report

2020-11-17 Thread Andrew
Just to confirm, I was able to compile 9.3.beta1 on macosx 10.0.1 running xcode 12.2 with homebrew. The following doctests failed with `make ptestlong`: sage -t --long --random-seed=0 src/sage/misc/sagedoc.py # 1 doctest failed sage -t --long --random-seed=0 src/sage/tests/cmdline.py # 1 docte

[sage-devel] Re: OS X Big Sur progress report

2020-11-16 Thread Andrew
Thanks very much for this Matthias. This is almost certainly my problem -- and I have to confess to user error as this was a hack I put in at one point to get around problems with an xcode update. I have deleted a bunch of spurious links like these and am now recompiling. It has already gotten

[sage-devel] Re: OS X Big Sur progress report

2020-11-16 Thread Matthias Koeppe
According to your log, you seem to have /usr/local/include/stdlib.h and /usr/local/include/math.h -- which seem to be breaking your giac build. This seems nonstandard. On Sunday, November 15, 2020 at 9:23:40 PM UTC-8 Andrew wrote: > Thanks for this John. Did you do anything special to compile

Re: [sage-devel] Re: OS X Big Sur progress report

2020-11-16 Thread Andrew
Dear Dima and John, Thanks for your hints. I have tried deleting ntl, flint and arb but I am still getting stuck on givaro. I'll try removing some more brew packages and see if this helps and report back. The list brew packages recommended by configure is: pandoc ffmpeg imagemagick texinfo

Re: [sage-devel] Re: OS X Big Sur progress report

2020-11-16 Thread Dima Pasechnik
On Mon, Nov 16, 2020 at 10:21 PM John H Palmieri wrote: > > > > On Monday, November 16, 2020 at 10:59:32 AM UTC-8 dim...@gmail.com wrote: >> >> If you have a random subset of partially outdated Homebrew packages, >> spiced up with manually installed random crap in /usrr/local/, there >> is no chan

Re: [sage-devel] Re: OS X Big Sur progress report

2020-11-16 Thread John H Palmieri
On Monday, November 16, 2020 at 10:59:32 AM UTC-8 dim...@gmail.com wrote: > If you have a random subset of partially outdated Homebrew packages, > spiced up with manually installed random crap in /usrr/local/, there > is no chance of getting things right on Homebrew. > > On Mon, Nov 16, 2020

Re: [sage-devel] Re: OS X Big Sur progress report

2020-11-16 Thread Dima Pasechnik
If you have a random subset of partially outdated Homebrew packages, spiced up with manually installed random crap in /usrr/local/, there is no chance of getting things right on Homebrew. On Mon, Nov 16, 2020 at 6:19 PM John H Palmieri wrote: > > In my experience, homebrew's "ntl" package can lea

Re: [sage-devel] Re: OS X Big Sur progress report

2020-11-16 Thread John H Palmieri
In my experience, homebrew's "ntl" package can lead to problems when building Sage, so if possible, try deleting it. I have these packages: % brew list autoconfghcjanssonmpcppl automakeghostscriptjpegmpfipython@3.8 bdw-gcgitlibat

Re: [sage-devel] Re: OS X Big Sur progress report

2020-11-15 Thread Dima Pasechnik
On Mon, Nov 16, 2020 at 5:23 AM Andrew wrote: > > Thanks for this John. Did you do anything special to compile sage with big > sur? I just tried: > > make distclean && source .homebrew-build-env && ./configure > --with-system-gfortran=no --with-system-openblas=no --with-system-gmp=no && > make

[sage-devel] Re: OS X Big Sur progress report

2020-11-15 Thread Andrew
Thanks for this John. Did you do anything special to compile sage with big sur? I just tried: make distclean && source .homebrew-build-env && ./configure --with-system-gfortran=no --with-system-openblas=no --with-system-gmp=no && make but the build fails with: Error building Sage. The follow