Some good news and some weird news: in my attempts to debug this, I uninstalled a bunch of my homebrew packages, and I got Sage to build and pass tests. Yay. Here's the strange part: if I add the package libpng, then Sage doesn't build. With these packages, it builds and passes tests (output from "brew list --versions"):
autoconf 2.69 automake 1.16.2 boost 1.72.0_1 cabextract 1.9.1 emacs-mac emacs-26.3-z-mac-7.9 gcc 9.2.0_1 9.3.0 gdbm 1.18.1 gettext 0.20.1 gmp 6.2.0 6.1.2_2 gnutls 3.6.12 icu4c 64.2 isl 0.22.1 0.21 0.18 jpeg 9d libdvdcss 1.4.2 libevent 2.1.11_1 libffi 3.2.1 libidn2 2.3.0 libmpc 1.1.0 libtasn1 4.14 4.16.0 libtiff 4.1.0 libunistring 0.9.10 mpfr 4.0.2 nettle 3.4.1 [email protected] 1.1.1d p11-kit 0.23.20 0.23.18.1 pkg-config 0.29.2 readline 8.0.4 sqlite 3.31.1 unbound 1.9.4 1.10.0 xz 5.2.5 If I then do "brew install libpng" and build Sage from scratch, kiwisolver fails to build. For some reason, something in the build process thinks that "-sdk" is a good flag to add to "g++": g++ -sdk macosx clang -bundle -undefined dynamic_lookup -L/Users/palmieri/Desktop/Sage_stuff/sage_builds/TESTING/png/sage-9.1.beta9/local/lib -Wl,-rpath,/Users/palmieri/Desktop/Sage_stuff/sage_builds/TESTING/png/sage-9.1.beta9/local/lib build/temp.macosx-10.14-x86_64-3.7/py/kiwisolver.o build/temp.macosx-10.14-x86_64-3.7/py/constraint.o build/temp.macosx-10.14-x86_64-3.7/py/expression.o build/temp.macosx-10.14-x86_64-3.7/py/solver.o build/temp.macosx-10.14-x86_64-3.7/py/strength.o build/temp.macosx-10.14-x86_64-3.7/py/term.o build/temp.macosx-10.14-x86_64-3.7/py/variable.o -o build/lib.macosx-10.14-x86_64-3.7/kiwisolver.cpython-37m-darwin.so clang: error: unknown argument: '-sdk' clang: error: no such file or directory: 'macosx' clang: error: no such file or directory: 'clang' error: command 'g++' failed with exit status 1 I didn't see this before, so if I add enough other packages, this problem will somehow resolve itself. This is specific to 9.1.beta9 (i.e., using the system python3): kiwisolver builds with 9.1.beta8 and these homebrew packages. On Monday, March 30, 2020 at 3:59:30 PM UTC-7, John H Palmieri wrote: > > I see the same in the log file for the Python 2 build. I wonder if this > has to do with upgrading Xcode, which I seem to have done 6 days ago. To be > clear, yesterday and today I have built 9.1.beta8 + Python 3 and 9.1.beta9 > + Python 2, both successfully, despite this crash. It's 9.1.beta9 + Python > 3 which is causing problems. It also seems to be using the Apple Python 3, > /usr/bin/python3, not the one installed by homebrew. > > For what it's worth: > > - I don't see this crash message from config.log files from a few weeks > ago. > - the message refers to a file > > /Users/palmieri/Library/Logs/DiagnosticReports/clang_<YYYY-MM-DD-HHMMSS>_<hostname>.crash, > > but there is no such file. > > > > On Monday, March 30, 2020 at 1:44:41 PM UTC-7, Matthias Köppe wrote: >> >> From your config.log ... rather suspicious: >> >> configure:10189: g++ -std=gnu++11 -o conftest -g -O2 conftest.cpp -lgmp >> -lm >&5 >> configure:10189: $? = 0 >> configure:10206: result: -lgmp >> configure:10231: will use system package and not install SPKG mpir >> configure:10265: checking absolute name of <gmp.h> >> configure:10272: checking for gmp.h >> configure:10272: result: yes >> clang: error: unable to execute command: Broken pipe: 13 >> clang: error: clang frontend command failed due to signal (use -v to see >> invocation) >> Apple clang version 11.0.3 (clang-1103.0.32.29) >> Target: x86_64-apple-darwin19.3.0 >> Thread model: posix >> InstalledDir: >> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin >> clang: note: diagnostic msg: PLEASE submit a bug report to >> http://developer.apple.com/bugreporter/ and include the crash backtrace, >> preprocessed source, and associated run script. >> clang: note: diagnostic msg: >> ******************** >> >> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: >> Preprocessed source(s) and associated run script(s) are located at: >> clang: note: diagnostic msg: >> /var/folders/cp/n8wtqs490tq5psknff1hv9qr0000gn/T/conftest-d428b4.cpp >> clang: note: diagnostic msg: >> /var/folders/cp/n8wtqs490tq5psknff1hv9qr0000gn/T/conftest-d428b4.sh >> clang: note: diagnostic msg: Crash backtrace is located in >> clang: note: diagnostic msg: >> /Users/palmieri/Library/Logs/DiagnosticReports/clang_<YYYY-MM-DD-HHMMSS>_<hostname>.crash >> clang: note: diagnostic msg: (choose the .crash file that corresponds to >> your crash) >> clang: note: diagnostic msg: >> >> ******************** >> configure:10296: result: ///usr/local/include/gmp.h >> configure:10332: result: using GMP-compatible library from the system >> ## ---------------------------------------------------- ## >> ## Checking whether SageMath should install SPKG gmp... ## >> ## ---------------------------------------------------- ## >> configure:10415: will use system package and not install SPKG gmp >> >> >> >> This seems to come from AX_ABSOLUTE_HEADER >> >> >> >> On Monday, March 30, 2020 at 12:18:41 PM UTC-4, John H Palmieri wrote: >>> >>> >>> config.log attached. >>> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/f9c7d952-233e-468d-bf16-43c73af1d4a3%40googlegroups.com.
