trouble compiling development version

152 views
Skip to first unread message

Anne Schilling

unread,
Sep 1, 2020, 1:13:22 PM9/1/20
to sage-devel
Hi!

I am having trouble (once again) to compile the latest development version of sage, see


This is on MacOS 10.15.6.

Any ideas?

Anne

....
[maxima-5.44.0] Copying package files from temporary location /Applications/sage/local/var/tmp/sage/build/maxima-5.44.0/inst to /Applications/sage/local
[maxima-5.44.0] Successfully installed maxima-5.44.0
[maxima-5.44.0] Deleting temporary build directory
[maxima-5.44.0] /Applications/sage/local/var/tmp/sage/build/maxima-5.44.0
[maxima-5.44.0] Finished installing maxima-5.44.0
[gfortran-9.2.0] Finished installing gfortran-9.2.0
make[2]: *** [all-start] Error 2

real    202m12.303s
user    144m55.131s
sys    25m56.364s
***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package:         kiwisolver-1.0.1
  last build time: Sep 1 02:41
  log file:        /Applications/sage/logs/pkgs/kiwisolver-1.0.1.log
  build directory: /Applications/sage/local/var/tmp/sage/build/kiwisolver-1.0.1

It is safe to delete any log files and build directories, but they
contain information that is helpful for debugging build problems.
WARNING: If you now run 'make' again, the build directory of the
same version of the package will, by default, be deleted. Set the
environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.

make[1]: *** [all-start] Error 1
make: *** [all] Error 2

Matthias Koeppe

unread,
Sep 1, 2020, 1:52:29 PM9/1/20
to sage-devel
Please post the top-level config.log too

Reimundo Heluani

unread,
Sep 1, 2020, 1:54:06 PM9/1/20
to sage-...@googlegroups.com
There are a bunch of errors like

error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.6" but "10.9" during configure

Did you run configure before make?

R
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Anne Schilling

unread,
Sep 1, 2020, 5:36:19 PM9/1/20
to sage-...@googlegroups.com
Here is the top level log file:


I did run ./configure before make.

Anne

Dima Pasechnik

unread,
Sep 1, 2020, 6:36:28 PM9/1/20
to sage-devel
On Tue, Sep 1, 2020 at 6:13 PM Anne Schilling <anne1.s...@gmail.com> wrote:
>
> Hi!
>
> I am having trouble (once again) to compile the latest development version of sage, see
>
> https://www.math.ucdavis.edu/~anne/kiwisolver-1.0.1.log
>
> This is on MacOS 10.15.6.
>
> Any ideas?
see
https://kiwisolver.readthedocs.io/en/latest/basis/installation.html
it says
---------------------------------------------------------------
For MacOSX users on OSX Mojave, one needs to set
MACOSX_DEPLOYMENT_TARGET to higher than 10.9 to force the compiler to
use the new C++ stdlib:

$ export MACOSX_DEPLOYMENT_TARGET=10.10
---------------------------------------------------------------

I'd do this export and hit "make" again

HTH
Dima
> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/0505a395-a133-47b1-956d-0334e07f9cedo%40googlegroups.com.

Zachary Scherr

unread,
Sep 1, 2020, 6:49:12 PM9/1/20
to sage-devel
You said that you are running 10.15.6 but something looks very bizarre with the python3 that configure is picking up.  It looks like it is using

/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7

since this python is first in your PATH.

Could you try running this python and then issuing:

>>> import sysconfig
>>> sysconfig.get_config_var('MACOSX_DEPLOYMENT_TARGET')

If you see it saying '10.9' then this might be related to your problem.

On my Catalina, configure finds python3 in /usr/bin, and if I issue those same commands I get '10.14'.  So maybe your PATH is causing sage to find an older version of python 3 which is causing things to mess up.  Maybe somebody with more experience can chime in, but I would guess that this is related to your problem.

Zachary Scherr

unread,
Sep 1, 2020, 6:56:05 PM9/1/20
to sage-devel
Also, it says that you have homebrew on your system.  Does 'brew doctor' complain about having python on your path? Maybe you might want to try to delete all of the old versions of python on your system and remove them from your PATH.

You might also consider following the homebrew recommendations (installing gcc@9 will stop gfortran 9 from compiling from scratch) and then running "source /Applications/sage/.homebrew-build-env" before you configure and make.

Matthias Koeppe

unread,
Sep 1, 2020, 7:41:07 PM9/1/20
to sage-devel
Could you also post the output that the command "env" gives?

Anne Schilling

unread,
Sep 1, 2020, 10:27:06 PM9/1/20
to sage-devel
Thank you, everyone, for your comments! The laptop indeed used the wrong python3 configuration. This is likely due to the fact that I copied all my files from an old laptop over, so it got confused. Sage builds now again!

Thank you,

Anne
Reply all
Reply to author
Forward
0 new messages