MacOS Catalina: sagenb compilation problem

42 views
Skip to first unread message

Rob Gross

unread,
Nov 1, 2019, 11:24:47 PM11/1/19
to sage-devel
Hi,

I managed to find advice about compiling gcc and gfortran on Catalina (summary in a moment), and now I ran into another problem compiling sage from source (not upgrading).  The attached log file shows the error message when I typed "make -j4" and watched the compilation nearly succeed.  Any ideas about how to resolve this error?

As for compiling gfortran on Catalina:  the recommendation (which worked for me) is to create a new directory which mostly contains soft links to the standard system files:

lrwxr-xr-x   1 root  wheel   60 Oct 31 20:28 Library@ -> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/Library/
lrwxr-xr-x   1 root  wheel   59 Oct 31 20:28 System@ -> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/
drwxr-xr-x   7 root  wheel  224 Oct 31 20:29 usr/

and usr looks like:

lrwxr-xr-x    1 root  wheel    60 Oct 31 20:28 bin@ -> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/bin/
drwxr-xr-x  270 root  wheel  8640 Oct 31 20:31 include/
lrwxr-xr-x    1 root  wheel    59 Oct 31 20:29 lib@ -> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/lib
lrwxr-xr-x    1 root  wheel    64 Oct 31 20:29 libexec@ -> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/libexec/
lrwxr-xr-x    1 root  wheel    62 Oct 31 20:29 share@ -> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/share/

Then I had to copy all of /Library.../include into my {new directory}/usr/include, and patch Availability.h following line 300:

...
#ifndef __OSX_AVAILABLE_STARTING
#define __OSX_AVAILABLE_STARTING(_osx, _ios)
#define __OSX_AVAILABLE_BUT_DEPRECATED(_osxIntro, _osxDep, _iosIntro, _iosDep)
#define __OSX_AVAILABLE_BUT_DEPRECATED_MSG(_osxIntro, _osxDep, _iosIntro, _iosDep, _msg)
#endif

#if defined(__has_feature)
...

Then "./configure gcc/gfortran  --with-sysroot=new_dummy_directory" worked, at least for me.

Thanks, as always.--Rob
sagenb-1.1.2.log

Dima Pasechnik

unread,
Nov 2, 2019, 2:19:33 AM11/2/19
to sage-devel
the error is not in sagenb, in fact.
Try starting Sage as

./sage

and send us the error message (and the file the error message asks you to send)

We need to do something about this "non"-error, it keeps confusing people.
> --
> 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/6bbd60fe-13d1-420f-8060-2ae8ea22f020%40googlegroups.com.

Rob Gross

unread,
Nov 2, 2019, 3:26:40 PM11/2/19
to sage-devel
Thank you.  I should have done that in my first posting.  I attach the crash report.

I have a suspicion that this is not going to be sufficient, but at least you can tell me what I should post next.
Sage_crash_report.txt
Reply all
Reply to author
Forward
0 new messages