Meta-ticket: Support Xcode 12

[mkoeppe]

Xcode 12 was publicly released on 2020-09-16.

Sage does not build from source using Xcode 12.2 beta, released 2020.09.17, clang version 12.0.0 (clang-1200.0.32.4)

• https://groups.google.com/d/msg/sage-support/ZLgu-1pi6nc/W7Hqe7AgAgAJ
• https://github.com/mkoeppe/sage/runs/1059961873

Failing packages (blockers):

• gf2x gf2x build with Xcode 12 #30593
• ecm fix ecm on macOS Xcode 12 #30600
• symmetrica fix symmetrica for xcode 12 #30608 or Upgrade to symmetrica-3.0.1 #29061
• ecl ecl build with Xcode 12 #30594
• scipy fix scipy for XCode 12 #30604

Failing packages with replacements available via homebrew:

• openblas Fix openblas to build with Xcode 12 #30610
• readline Upgrade readline to 8.0 #30603
• gmp upgrade GMP to version 6.2.0 #30625
• mpir
• gsl (?)
• r fix R on macOS xcode 12 #30631

Failing optional packages:

• rubiks (see also Downgrade rubiks to optional #28022)
• gap_packages (Fix gap_packages for Xcode 12 #30729)
• polylib (Update isl + polylib + barvinok packages #33758)

Failing experimental packages:

• gdb, valgrind (to be removed in Reduce outdated gdb and valgrind packages to dummy script packages #30158)
• gap3, cocoalib, awali, libtheora, surf, scipoptsuite https://github.com/mkoeppe/sage/actions/runs/289319580

Tickets:

• GH Actions: Test also with Xcode 12 beta #30487 - GH Actions: Test also with Xcode 12 beta
• Upgrade: Python 3.8.5 #27754 - Upgrade: Python 3.8.5
• Downgrade rubiks to optional #28022 - Downgrade rubiks to optional
• Accept /usr/bin/python3 from XCode 12.3 on macOS 10.15 (Catalina) and 11 (Big Sur) #31227 - Accept /usr/bin/python3 from XCode 12.3 on macOS 10.15 (Catalina)

Follow-up:

• Meta-ticket: support macOS 11 Big Sur #30651 - Meta-ticket: support macOS 11

CC: @jhpalmieri @dimpase @slel @vbraun

Component: porting

Keywords: macOS, Xcode

Reviewer: Dima Pasechnik

Issue created by migration from https://trac.sagemath.org/ticket/30494

[mkoeppe]

Description changed:

--- 
+++ 
@@ -1,8 +1,15 @@
 Sage does not build from source using Xcode 12 beta.
 
 - https://groups.google.com/d/msg/sage-support/ZLgu-1pi6nc/W7Hqe7AgAgAJ
-- 
+- https://github.com/mkoeppe/sage/runs/1059961873
 
+Failing packages:
+- gf2x
+- ecm
+- symmetrica
+- rubiks
+- ecl
+- scipy
 
 Tickets: 
 - #30487 - GH Actions: Test also with Xcode 12 beta

[mkoeppe]

Description changed:

--- 
+++ 
@@ -13,4 +13,4 @@
 
 Tickets: 
 - #30487 - GH Actions: Test also with Xcode 12 beta
-
+- #28022 - Downgrade `rubiks` to optional

[mkoeppe]

Description changed:

--- 
+++ 
@@ -13,4 +13,5 @@
 
 Tickets: 
 - #30487 - GH Actions: Test also with Xcode 12 beta
+- #27754 - Upgrade: Python 3.8.5
 - #28022 - Downgrade `rubiks` to optional

[jhpalmieri]

comment:4

For what it's worth, I was trying to build without setting MACOSX_DEPLOYMENT_TARGET at all: I removed those lines from src/bin/sage-env.

[mkoeppe]

comment:5

Note that these lines are only executed when using python3 installed from spkg, not system python

[dimpase]

comment:6

looks like this should wait till 9.3

[jhpalmieri]

comment:7

Sure, Big Sur is still in beta.

[jhpalmieri]

comment:9

Xcode 12 has been released, and it causes breakage with Catalina, so perhaps this should be a blocker for 9.2. (For example I now cannot build Sage: I upgraded a laptop to a beta release of Big Sur, and on my main machine Xcode updated itself to version 12 overnight.)

[mkoeppe]

comment:10

I agree. It would be good to figure out if the upstream maintainers of these packages are already aware of these issues.

[dimpase]

comment:11

Can we score an https://en.wikipedia.org/wiki/Developer_Transition_Kit_(2020) - and Apple ARM prototype for developers somehow?
It might be very useful for testing. Probably a Raspberry Pi with a 64-bit OS comes close, but not as much.

[mkoeppe]

comment:12

This is unrelated to this ticket.

[mkoeppe]

comment:13

I have opened #30592 (Meta-ticket: Port to Apple silicon) for that. Let's keep the present ticket focused please. No new hardware is required.

[jhpalmieri]

comment:14

It seems that when configuring gf2x and ecl, at least, something like -Wall is being used. I see this kind of thing in the config.log files for those:

conftest.c:4:3: error: implicitly declaring library function 'exit' with type 'void (int) __attribute__((noreturn))' [-Werror,-Wimplicit-function-declaration]
  exit(0);
  ^
conftest.c:4:3: note: include the header <stdlib.h> or explicitly provide a declaration for 'exit'
1 error generated.

Is there some setting in Xcode's command-line tools that has changed, causing these errors?

[jhpalmieri]

comment:15

Similar with ecm:

configure:13286: clang -O2 -pedantic -fomit-frame-pointer -m64 -mtune=nehalem -march=nehalem  -c conftes1.c >&5 && clang -O2 -pedantic -fomit-frame-pointer -m64 -mtune=nehalem -march=nehalem -c conftes2.s >&5 && clang -O2 -pedantic -fomit-frame-pointer -m64 -mtune=nehalem -march=nehalem  conftes1.o conftes2.o >&5
conftes1.c:4:1: warning: type specifier missing, defaults to 'int' [-Wimplicit-int]
main () { underscore_test(); }
^
conftes1.c:4:11: error: implicit declaration of function 'underscore_test' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
main () { underscore_test(); }
          ^
1 warning and 1 error generated.

[emmanuelthome]

comment:16

Hi,

I just learned about this ticket. (me = upstream gf2x)

I don't have access to a box of this kind, so I can't test. (all I have is macOS 10.15.5 + XCode 11.6).

It looks like latest xcode doesn't like the tests that are generated by autotools, right ? If yes, does a autoreconf with fresh autotools fix the problem ?

E.