trouble compiling latest sage development version
194 views
Skip to first unread message
Anne Schilling
Sep 30, 2016, 1:10:15 PM9/30/16
to sage-devel
Hi!
I am having trouble compiling the latest sage development branch:
...
[openblas-0.2.15] correctly and load a subshell for you to debug the error:
[openblas-0.2.15] (cd '/Applications/sage/local/var/tmp/sage/build/openblas-0.2.15' && '/Applications/sage/sage' --sh)
[openblas-0.2.15] When you are done debugging, you can type "exit" to leave the subshell.
[openblas-0.2.15] ************************************************************************
make[2]: *** [/Applications/sage/local/var/lib/sage/installed/openblas-0.2.15] Error 1
make[1]: *** [all] Error 2
real 1m11.086s
user 6m22.998s
sys 1m31.258s
***************************************************************
Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all'):
* package: givaro-4.0.2
log file: /Applications/sage/logs/pkgs/givaro-4.0.2.log
build directory: /Applications/sage/local/var/tmp/sage/build/givaro-4.0.2
* package: ntl-9.8.1.p0
log file: /Applications/sage/logs/pkgs/ntl-9.8.1.p0.log
build directory: /Applications/sage/local/var/tmp/sage/build/ntl-9.8.1.p0
* package: openblas-0.2.15
log file: /Applications/sage/logs/pkgs/openblas-0.2.15.log
build directory: /Applications/sage/local/var/tmp/sage/build/openblas-0.2.15
* package: sage-7.1.rc0
log file: /Applications/sage/logs/pkgs/sage-7.1.rc0.log
build directory: /Applications/sage/local/var/tmp/sage/build/sage-7.1.rc0
* documentation: dochtml
log file: /Applications/sage/logs/pkgs/../dochtml.log
The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
make: *** [all] Error 1
This is running on OSX 10.10.5.
Any idea what the problem might be?
Best,
Anne
I am having trouble compiling the latest sage development branch:
...
[openblas-0.2.15] correctly and load a subshell for you to debug the error:
[openblas-0.2.15] (cd '/Applications/sage/local/var/tmp/sage/build/openblas-0.2.15' && '/Applications/sage/sage' --sh)
[openblas-0.2.15] When you are done debugging, you can type "exit" to leave the subshell.
[openblas-0.2.15] ************************************************************************
make[2]: *** [/Applications/sage/local/var/lib/sage/installed/openblas-0.2.15] Error 1
make[1]: *** [all] Error 2
real 1m11.086s
user 6m22.998s
sys 1m31.258s
***************************************************************
Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all'):
* package: givaro-4.0.2
log file: /Applications/sage/logs/pkgs/givaro-4.0.2.log
build directory: /Applications/sage/local/var/tmp/sage/build/givaro-4.0.2
* package: ntl-9.8.1.p0
log file: /Applications/sage/logs/pkgs/ntl-9.8.1.p0.log
build directory: /Applications/sage/local/var/tmp/sage/build/ntl-9.8.1.p0
* package: openblas-0.2.15
log file: /Applications/sage/logs/pkgs/openblas-0.2.15.log
build directory: /Applications/sage/local/var/tmp/sage/build/openblas-0.2.15
* package: sage-7.1.rc0
log file: /Applications/sage/logs/pkgs/sage-7.1.rc0.log
build directory: /Applications/sage/local/var/tmp/sage/build/sage-7.1.rc0
* documentation: dochtml
log file: /Applications/sage/logs/pkgs/../dochtml.log
The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
make: *** [all] Error 1
This is running on OSX 10.10.5.
Any idea what the problem might be?
Best,
Anne
John H Palmieri
Sep 30, 2016, 6:03:45 PM9/30/16
to sage-devel
Hi Anne,
Here's a complete shot in the dark: has Xcode been updated recently on that machine, maybe automatically when you didn't notice? If you run "git status" (using the system's git) and it gives some funny error message about root access, this is what's going on. Run Xcode, agree to the new licensing agreement, and let it update whatever components it wants to update.
John
Here's a complete shot in the dark: has Xcode been updated recently on that machine, maybe automatically when you didn't notice? If you run "git status" (using the system's git) and it gives some funny error message about root access, this is what's going on. Run Xcode, agree to the new licensing agreement, and let it update whatever components it wants to update.
John
Anne Schilling
Sep 30, 2016, 7:53:38 PM9/30/16
to sage-devel
Hi John,
Thanks for your answer, but my git seems to work fine.
Even after 'make distclean && make' I still get an error. Here is the log. Any idea? Might this be related to
https://trac.sagemath.org/ticket/17635
Best, Anne ----- Found local metadata for givaro-4.0.2 Using cached file /Applications/sage/upstream/givaro-4.0.2.tar.gz givaro-4.0.2 ==================================================== Setting up build directory for givaro-4.0.2 Finished extraction **************************************************** Host system: Darwin lolita.local 14.5.0 Darwin Kernel Version 14.5.0: Wed Jul 29 02:26:53 PDT 2015; root:xnu-2782.40.9~1/RELEASE_X86_64 x86_64 **************************************************** C compiler: gcc C compiler version: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/Applications/sage/local/libexec/gcc/x86_64-apple-darwin14.5.0/4.9.3/lto-wrapper Target: x86_64-apple-darwin14.5.0 Configured with: ../src/configure --prefix=/Applications/sage/local --with-local-prefix=/Applications/sage/local --with-gmp=/Applications/sage/local --with-mpfr=/Applications/sage/local --with-mpc=/Applications/sage/local --with-system-zlib --disable-multilib --disable-nls --enable-languages=c,c++,fortran --disable-libitm --with-build-config=bootstrap-debug --without-isl --without-cloog Thread model: posix gcc version 4.9.3 (GCC) **************************************************** checking build system type... x86_64-apple-darwin14.5.0 checking host system type... x86_64-apple-darwin14.5.0 checking target system type... x86_64-apple-darwin14.5.0 checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... build-aux/install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for rm... /bin/rm checking whether to enable maintainer-specific portions of Makefiles... no ----------------------------------------------- checking whether to enable debugging options in the library... no checking whether to enable profiling everything in the library... no checking whether to enable warnings when compiling the library... no checking whether to inline or not most of the code ?... no ----------------------------------------------- checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for family name of compiler... gcc (GCC) 4.9.3 checking whether g++ supports C++11 features by default... no checking whether g++ supports C++11 features with -std=gnu++11... yes checking how to run the C++ preprocessor... g++ -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking how to print strings... printf checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking for a sed that does not truncate output... /usr/bin/sed checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... ld checking if the linker (ld) is GNU ld... no checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm checking the name lister (/usr/bin/nm) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 196608 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert x86_64-apple-darwin14.5.0 file names to x86_64-apple-darwin14.5.0 format... func_convert_file_noop checking how to convert x86_64-apple-darwin14.5.0 file names to toolchain format... func_convert_file_noop checking for ld option to reload object files... -r checking for objdump... no checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for archiver @FILE support... no checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm output from gcc object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking for dsymutil... dsymutil checking for nmedit... nmedit checking for lipo... lipo checking for otool... otool checking for otool64... no checking for -single_module linker flag... yes checking for -exported_symbols_list linker flag... yes checking for -force_load linker flag... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fno-common -DPIC checking if gcc PIC flag -fno-common -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (ld) supports shared libraries... yes checking dynamic linker characteristics... darwin14.5.0 dyld checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking how to run the C++ preprocessor... g++ -E checking for ld used by g++... ld checking if the linker (ld) is GNU ld... no checking whether the g++ linker (ld) supports shared libraries... yes checking for g++ option to produce PIC... -fno-common -DPIC checking if g++ PIC flag -fno-common -DPIC works... yes checking if g++ static flag -static works... no checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (ld) supports shared libraries... yes checking dynamic linker characteristics... darwin14.5.0 dyld checking how to hardcode library paths into programs... immediate ----------------------------------------------- START GIVARO CONFIG ----------------------------------------------- ----------------------------------------------- ----------------------------------------------- SIMD enabled checking for gcc __builtin_cpu_init function... yes checking for x86 mmx instruction support... yes checking for x86 popcnt instruction support... yes checking for x86 sse instruction support... yes checking for x86 sse2 instruction support... yes checking for x86 sse3 instruction support... yes checking for x86 sse4.1 instruction support... yes checking for x86 sse4.2 instruction support... yes checking for x86 sse4a instruction support... no checking for x86 avx instruction support... yes checking for x86 avx2 instruction support... yes checking for x86 avx512f instruction support... no checking for x86 fma instruction support... yes checking for x86 fma4 instruction support... no checking for x86 bmi instruction support... no checking for x86 bmi2 instruction support... no checking size of char... 1 checking size of short... 2 checking size of int... 4 checking size of long... 8 checking size of long long... 8 checking size of __int64_t... 8 checking for __int128_t... yes checking for ANSI C header files... (cached) yes checking float.h usability... yes checking float.h presence... yes checking for float.h... yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking for stdint.h... (cached) yes checking pthread.h usability... yes checking pthread.h presence... yes checking for pthread.h... yes checking whether byte ordering is bigendian... no Creating symbolic link for compilation ----------------------------------------------- ----------------------------------------------- checking for GMP >= 4.0.0 with cxx enabled... found checking whether to build documentation... no checking whether dot works... yes ----------------------------------------------- END GIVARO CONFIG ----------------------------------------------- checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating givaro-config config.status: creating givaro-makefile config.status: creating src/Makefile config.status: creating src/kernel/Makefile config.status: creating src/kernel/system/Makefile config.status: creating src/kernel/memory/Makefile config.status: creating src/kernel/gmp++/Makefile config.status: creating src/kernel/integer/Makefile config.status: creating src/kernel/bstruct/Makefile config.status: creating src/kernel/rational/Makefile config.status: creating src/kernel/recint/Makefile config.status: creating src/kernel/field/Makefile config.status: creating src/kernel/ring/Makefile config.status: creating src/library/Makefile config.status: creating src/library/vector/Makefile config.status: creating src/library/tools/Makefile config.status: creating src/library/poly1/Makefile config.status: creating src/library/matrix/Makefile config.status: creating macros/Makefile config.status: creating benchmarks/Makefile config.status: creating examples/Makefile config.status: creating examples/FiniteField/Makefile config.status: creating examples/Integer/Makefile config.status: creating examples/Rational/Makefile config.status: creating examples/RecInt/Makefile config.status: creating examples/Polynomial/Makefile config.status: creating tests/Makefile config.status: creating docs/Makefile config.status: creating givaro.pc config.status: creating config.h config.status: executing givaro-config.h commands config.status: creating givaro-config.h - prefix __GIVARO for config.h defines config.status: executing depfiles commands config.status: executing libtool commands ----------------------------------------------- make all-recursive Making all in src Making all in kernel Making all in system /bin/sh ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../src/kernel/memory -O2 -Wall -g -DNDEBUG -UGIVARO_DEBUG -UDEBUG -I/Applications/sage/local//include -fPIC -I"/Applications/sage/local/include" -std=gnu++11 -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -mavx -mavx2 -mfma -mfpmath=sse -fabi-version=6 -c -o givbasictype.lo givbasictype.C libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../src/kernel/memory -O2 -Wall -g -DNDEBUG -UGIVARO_DEBUG -UDEBUG -I/Applications/sage/local//include -fPIC -I/Applications/sage/local/include -std=gnu++11 -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -mavx -mavx2 -mfma -mfpmath=sse -fabi-version=6 -c givbasictype.C -fno-common -DPIC -o .libs/givbasictype.o libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../src/kernel/memory -O2 -Wall -g -DNDEBUG -UGIVARO_DEBUG -UDEBUG -I/Applications/sage/local//include -fPIC -I/Applications/sage/local/include -std=gnu++11 -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -mavx -mavx2 -mfma -mfpmath=sse -fabi-version=6 -c givbasictype.C -o givbasictype.o >/dev/null 2>&1 /bin/sh ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../src/kernel/memory -O2 -Wall -g -DNDEBUG -UGIVARO_DEBUG -UDEBUG -I/Applications/sage/local//include -fPIC -I"/Applications/sage/local/include" -std=gnu++11 -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -mavx -mavx2 -mfma -mfpmath=sse -fabi-version=6 -c -o giverror.lo giverror.C libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../src/kernel/memory -O2 -Wall -g -DNDEBUG -UGIVARO_DEBUG -UDEBUG -I/Applications/sage/local//include -fPIC -I/Applications/sage/local/include -std=gnu++11 -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -mavx -mavx2 -mfma -mfpmath=sse -fabi-version=6 -c giverror.C -fno-common -DPIC -o .libs/giverror.o libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../src/kernel/memory -O2 -Wall -g -DNDEBUG -UGIVARO_DEBUG -UDEBUG -I/Applications/sage/local//include -fPIC -I/Applications/sage/local/include -std=gnu++11 -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -mavx -mavx2 -mfma -mfpmath=sse -fabi-version=6 -c giverror.C -o giverror.o >/dev/null 2>&1 /bin/sh ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../src/kernel/memory -O2 -Wall -g -DNDEBUG -UGIVARO_DEBUG -UDEBUG -I/Applications/sage/local//include -fPIC -I"/Applications/sage/local/include" -std=gnu++11 -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -mavx -mavx2 -mfma -mfpmath=sse -fabi-version=6 -c -o givinit.lo givinit.C libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../src/kernel/memory -O2 -Wall -g -DNDEBUG -UGIVARO_DEBUG -UDEBUG -I/Applications/sage/local//include -fPIC -I/Applications/sage/local/include -std=gnu++11 -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -mavx -mavx2 -mfma -mfpmath=sse -fabi-version=6 -c givinit.C -fno-common -DPIC -o .libs/givinit.o /var/folders/sq/gx2hlzhj315g48j_8r39s8p80000gp/T//ccleqUwl.s:517:no such instruction: `vzeroupper' /var/folders/sq/gx2hlzhj315g48j_8r39s8p80000gp/T//ccleqUwl.s:578:no such instruction: `vzeroupper' /var/folders/sq/gx2hlzhj315g48j_8r39s8p80000gp/T//ccleqUwl.s:591:no such instruction: `vzeroupper' /var/folders/sq/gx2hlzhj315g48j_8r39s8p80000gp/T//ccleqUwl.s:618:no such instruction: `vzeroupper' make[7]: *** [givinit.lo] Error 1 make[6]: *** [all-recursive] Error 1 make[5]: *** [all-recursive] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [all] Error 2 Error building givaro real 0m9.647s user 0m5.345s sys 0m4.427s ************************************************************************ Error installing package givaro-4.0.2 ************************************************************************ Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /Applications/sage/logs/pkgs/givaro-4.0.2.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /Applications/sage/local/var/tmp/sage/build/givaro-4.0.2 and type 'make' or whatever is appropriate. Instead, the following commands setup all environment variables correctly and load a subshell for you to debug the error: (cd '/Applications/sage/local/var/tmp/sage/build/givaro-4.0.2' && '/Applications/sage/sage' --sh) When you are done debugging, you can type "exit" to leave the subshell. ************************************************************************
Travis Scrimshaw
Sep 30, 2016, 9:52:06 PM9/30/16
to sage-devel
Perhaps this is from the same error as stack overflow post? I remember we had to have something with '-march=native' (on OSX?) in the past.
Best,
Travis
Best,
Travis
Francois Bissey
Sep 30, 2016, 10:08:35 PM9/30/16
to sage-...@googlegroups.com
Does the ntl failure look like anything reported at https://trac.sagemath.org/ticket/20779 ?
François
> --
> 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 post to this group, send email to sage-...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
François
> 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 post to this group, send email to sage-...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
Anne Schilling
Sep 30, 2016, 11:20:43 PM9/30/16
to sage-devel
I am not sure. I just compiled sage-7.3 released 2016-8-04 and it went fine, so I think it must be related
to some new patches in the new development branch ...
Anne
to some new patches in the new development branch ...
Anne
Volker Braun
Oct 1, 2016, 4:16:02 AM10/1/16
to sage-devel
My suggestion would be to upgrade to xcode 10.11, and then to the newer xcode that is available on osx 10.11 only. That linker should then properly support AVX instructions. Thats also the only OS/compiler version that we have a buildbot for (or receives updates from Apple for that matter).
Dima Pasechnik
Oct 1, 2016, 9:59:26 AM10/1/16
to sage-devel
On Saturday, October 1, 2016 at 8:16:02 AM UTC, Volker Braun wrote:
My suggestion would be to upgrade to xcode 10.11,
to OSX 10.11, that is...
leif
Oct 1, 2016, 1:55:58 PM10/1/16
to sage-...@googlegroups.com
Volker Braun wrote:
> My suggestion would be to upgrade to xcode 10.11, and then to the newer
> xcode that is available on osx 10.11 only. That linker should then
> properly support AVX instructions. Thats also the only OS/compiler
> version that we have a buildbot for (or receives updates from Apple for
> that matter).
Well, until then the spkg-install scripts (sh|c)ould catch this (Sage's
> My suggestion would be to upgrade to xcode 10.11, and then to the newer
> xcode that is available on osx 10.11 only. That linker should then
> properly support AVX instructions. Thats also the only OS/compiler
> version that we have a buildbot for (or receives updates from Apple for
> that matter).
GCC emitting instructions Apple's ancient assembler doesn't support).
It's weird Givaro's 'configure' claims AVX, AVX2 and FMA3 supported, but
neither BMI nor BMI2. (Haven't looked at the macros used though.)
-leif
Anne Schilling
Oct 11, 2016, 2:35:18 PM10/11/16
to sage-devel
Hi Volker,
Thanks for the suggestion. I upgraded to OSX 10.12 and installed the latest version command line xcode. Now I get the following
error (even when compiling the latest stable release of sage):
...
[maxima-5.35.1.p2] /usr/bin/install -c -m 644 ./z_transform/rtest_z_transform.mac /Applications/sage/local/share/maxima/5.35.1/share/z_transform/rtest_z_transform.mac
[maxima-5.35.1.p2] /usr/bin/install -c -m 644 ./z_transform/z_transform.mac /Applications/sage/local/share/maxima/5.35.1/share/z_transform/z_transform.mac
[maxima-5.35.1.p2] Making install in demo
[maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
[maxima-5.35.1.p2] /bin/sh /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh -d
[maxima-5.35.1.p2] test -z "/Applications/sage/local/share/maxima/5.35.1/demo" || .././install-sh -c -d "/Applications/sage/local/share/maxima/5.35.1/demo"
[maxima-5.35.1.p2] /usr/bin/install -c -m 644 cf.dem demo.dem eaton1.dem eaton2.dem ezgcd.dem hypgeo.dem macex.dem macro.dem newfac.dem romberg.dem sumcon.dem trgsmp.dem manual.demo plots.mac '/Applications/sage/local/share/maxima/5.35.1/demo'
[maxima-5.35.1.p2] Making install in plotting
[maxima-5.35.1.p2] test -z "/Applications/sage/local/libexec/maxima/5.35.1" || .././install-sh -c -d "/Applications/sage/local/libexec/maxima/5.35.1"
[maxima-5.35.1.p2] /bin/sh /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh -d
[maxima-5.35.1.p2] /usr/bin/install -c mgnuplot '/Applications/sage/local/libexec/maxima/5.35.1'
[maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
[maxima-5.35.1.p2] /bin/sh /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh -d
[maxima-5.35.1.p2]
[maxima-5.35.1.p2] Now installing the Maxima library as '/Applications/sage/local/lib/ecl//maxima.fas'...
[maxima-5.35.1.p2]
[maxima-5.35.1.p2] real 5m29.945s
[maxima-5.35.1.p2] user 4m48.551s
[maxima-5.35.1.p2] sys 0m36.527s
[maxima-5.35.1.p2] Successfully installed maxima-5.35.1.p2
[maxima-5.35.1.p2] Deleting temporary build directory
[maxima-5.35.1.p2] /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2
[maxima-5.35.1.p2] Finished installing maxima-5.35.1.p2.spkg
Thanks for the suggestion. I upgraded to OSX 10.12 and installed the latest version command line xcode. Now I get the following
error (even when compiling the latest stable release of sage):
...
[maxima-5.35.1.p2] /usr/bin/install -c -m 644 ./z_transform/rtest_z_transform.mac /Applications/sage/local/share/maxima/5.35.1/share/z_transform/rtest_z_transform.mac
[maxima-5.35.1.p2] /usr/bin/install -c -m 644 ./z_transform/z_transform.mac /Applications/sage/local/share/maxima/5.35.1/share/z_transform/z_transform.mac
[maxima-5.35.1.p2] Making install in demo
[maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
[maxima-5.35.1.p2] /bin/sh /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh -d
[maxima-5.35.1.p2] test -z "/Applications/sage/local/share/maxima/5.35.1/demo" || .././install-sh -c -d "/Applications/sage/local/share/maxima/5.35.1/demo"
[maxima-5.35.1.p2] /usr/bin/install -c -m 644 cf.dem demo.dem eaton1.dem eaton2.dem ezgcd.dem hypgeo.dem macex.dem macro.dem newfac.dem romberg.dem sumcon.dem trgsmp.dem manual.demo plots.mac '/Applications/sage/local/share/maxima/5.35.1/demo'
[maxima-5.35.1.p2] Making install in plotting
[maxima-5.35.1.p2] test -z "/Applications/sage/local/libexec/maxima/5.35.1" || .././install-sh -c -d "/Applications/sage/local/libexec/maxima/5.35.1"
[maxima-5.35.1.p2] /bin/sh /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh -d
[maxima-5.35.1.p2] /usr/bin/install -c mgnuplot '/Applications/sage/local/libexec/maxima/5.35.1'
[maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
[maxima-5.35.1.p2] /bin/sh /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh -d
[maxima-5.35.1.p2]
[maxima-5.35.1.p2] Now installing the Maxima library as '/Applications/sage/local/lib/ecl//maxima.fas'...
[maxima-5.35.1.p2]
[maxima-5.35.1.p2] real 5m29.945s
[maxima-5.35.1.p2] user 4m48.551s
[maxima-5.35.1.p2] sys 0m36.527s
[maxima-5.35.1.p2] Successfully installed maxima-5.35.1.p2
[maxima-5.35.1.p2] Deleting temporary build directory
[maxima-5.35.1.p2] /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2
[maxima-5.35.1.p2] Finished installing maxima-5.35.1.p2.spkg
make[1]: *** [all] Error 2
real 49m54.858s
user 145m38.154s
sys 18m47.495s
user 145m38.154s
sys 18m47.495s
***************************************************************
Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all'):
The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
make: *** [all] Error 1
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
make: *** [all] Error 1
Any further suggestions?
Anne
Anne
Francois Bissey
Oct 11, 2016, 2:48:46 PM10/11/16
to sage-...@googlegroups.com
John H Palmieri
Oct 11, 2016, 2:50:30 PM10/11/16
to sage-devel
On Tuesday, October 11, 2016 at 11:35:18 AM UTC-7, Anne Schilling wrote:
Hi Volker,
Thanks for the suggestion. I upgraded to OSX 10.12 and installed the latest version command line xcode. Now I get the following
error (even when compiling the latest stable release of sage):
Volker actually suggested upgrading to OS X 10.11. Sage does not build out of the box on OS X 10.12 yet, but there is a branch at https://trac.sagemath.org/ticket/21567 which works for me. You may need to do "sage -f python2" to force it to reinstall Python, since on OS X 10.12, Sage fails to build Python correctly (although it thinks it has). So: (1) get the branch from #21567, (2) do "sage -f python2", and then "make", or (2') do "make distclean" followed by "make". And keep your fingers crossed.
John
Anne Schilling
Oct 11, 2016, 3:10:32 PM10/11/16
to sage-devel
I guess I was overzealous upgrading to OSX10.12.
Thanks John for your suggestions! With ticket 21567, I do not seem to get very far:
make
make -j4 build/make/Makefile
./bootstrap -d
rm -rf config configure build/make/Makefile-auto.in
./bootstrap: line 31: aclocal: command not found
Bootstrap failed, downloading required files instead.
Traceback (most recent call last):
File "/Applications/sage/build/bin/sage-download-file", line 27, in <module>
from sage_bootstrap.download.cmdline import run_safe
File "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", line 7, in <module>
from sage_bootstrap.download.transfer import Download
File "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", line 23, in <module>
from sage_bootstrap.compat import urllib
File "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 23, in <module>
import urllib
File "/Applications/sage/local/lib/python/urllib.py", line 1414, in <module>
from _scproxy import _get_proxy_settings, _get_proxies
ImportError: No module named _scproxy
Error: downloading configure-183.tar.gz failed
make[1]: *** [configure] Error 1
make: *** [all] Error 2
Best,
Anne
Thanks John for your suggestions! With ticket 21567, I do not seem to get very far:
make
make -j4 build/make/Makefile
./bootstrap -d
rm -rf config configure build/make/Makefile-auto.in
./bootstrap: line 31: aclocal: command not found
Bootstrap failed, downloading required files instead.
Traceback (most recent call last):
File "/Applications/sage/build/bin/sage-download-file", line 27, in <module>
from sage_bootstrap.download.cmdline import run_safe
File "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", line 7, in <module>
from sage_bootstrap.download.transfer import Download
File "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", line 23, in <module>
from sage_bootstrap.compat import urllib
File "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 23, in <module>
import urllib
File "/Applications/sage/local/lib/python/urllib.py", line 1414, in <module>
from _scproxy import _get_proxy_settings, _get_proxies
ImportError: No module named _scproxy
Error: downloading configure-183.tar.gz failed
make[1]: *** [configure] Error 1
make: *** [all] Error 2
Best,
Anne
Anne Schilling
Oct 11, 2016, 3:19:47 PM10/11/16
to sage-devel
Well, in fact now no matter what I do, I get this error. Even from the master branch:
make distclean
make distclean
make -j4 build/make/Makefile
./bootstrap -d
rm -rf config configure build/make/Makefile-auto.in
./bootstrap: line 29: aclocal: command not found
Bootstrap failed, downloading required files instead.
Traceback (most recent call last):
File "/Applications/sage/build/bin/sage-download-file", line 27, in <module>
from sage_bootstrap.download.cmdline import run_safe
File "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", line 7, in <module>
from sage_bootstrap.download.transfer import Download
File "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", line 23, in <module>
from sage_bootstrap.compat import urllib
File "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 23, in <module>
import urllib
File "/Applications/sage/local/lib/python/urllib.py", line 1414, in <module>
from _scproxy import _get_proxy_settings, _get_proxies
ImportError: No module named _scproxy
Error: downloading configure-176.tar.gz failed
make[1]: *** [configure] Error 1
make: *** [build-clean] Error 2
John H Palmieri
Oct 11, 2016, 3:47:47 PM10/11/16
to sage-devel
Right, Sage's Python is broken. Try deleting sage/local/bin/python and python2, and also sage/local/lib/python2.7 and sage/local/lib/libpython2.7.dylib. Then the build process should use the system's Python until Sage builds a working one.
Dima Pasechnik
Oct 11, 2016, 4:26:22 PM10/11/16
to sage-devel
On Tuesday, October 11, 2016 at 7:47:47 PM UTC, John H Palmieri wrote:
Right, Sage's Python is broken. Try deleting sage/local/bin/python and python2, and also sage/local/lib/python2.7 and sage/local/lib/libpython2.7.dylib. Then the build process should use the system's Python until Sage builds a working one.
hmm, I don't understand. I think I tried starting from 'make distclean' and still got stuck at that No module named _scproxy thing.
François Bissey
Oct 11, 2016, 4:39:34 PM10/11/16
to sage-...@googlegroups.com
On 12/10/16 09:26, Dima Pasechnik wrote:
>
>
> On Tuesday, October 11, 2016 at 7:47:47 PM UTC, John H Palmieri wrote:
>
> Right, Sage's Python is broken. Try deleting sage/local/bin/python
> and python2, and also sage/local/lib/python2.7 and
> sage/local/lib/libpython2.7.dylib. Then the build process should use
> the system's Python until Sage builds a working one.
>
>
> hmm, I don't understand. I think I tried starting from 'make distclean'
> and still got stuck at that No module named _scproxy thing.
I know there are safe guards in sage-env but nonetheless once the broken
>
>
> On Tuesday, October 11, 2016 at 7:47:47 PM UTC, John H Palmieri wrote:
>
> Right, Sage's Python is broken. Try deleting sage/local/bin/python
> and python2, and also sage/local/lib/python2.7 and
> sage/local/lib/libpython2.7.dylib. Then the build process should use
> the system's Python until Sage builds a working one.
>
>
> hmm, I don't understand. I think I tried starting from 'make distclean'
> and still got stuck at that No module named _scproxy thing.
python is installed it has to be cleaned manually. It is my experience
too. It is an OS X (mainly Sierra right now) thing only.
Francois
John H Palmieri
Oct 11, 2016, 5:15:06 PM10/11/16
to sage-devel
On Tuesday, October 11, 2016 at 1:26:22 PM UTC-7, Dima Pasechnik wrote:
On Tuesday, October 11, 2016 at 7:47:47 PM UTC, John H Palmieri wrote:Right, Sage's Python is broken. Try deleting sage/local/bin/python and python2, and also sage/local/lib/python2.7 and sage/local/lib/libpython2.7.dylib. Then the build process should use the system's Python until Sage builds a working one.hmm, I don't understand. I think I tried starting from 'make distclean' and still got stuck at that No module named _scproxy thing.
Are you saying you did this with the 'develop' branch or with the branch from #21567? I can understand the former; that's why we have #21567.
When we build Python on OS X, we should test that _scproxy builds correctly before declaring the build a success.
John
John H Palmieri
Oct 11, 2016, 5:35:20 PM10/11/16
to sage-devel
On Tuesday, October 11, 2016 at 2:15:06 PM UTC-7, John H Palmieri wrote:
On Tuesday, October 11, 2016 at 1:26:22 PM UTC-7, Dima Pasechnik wrote:
On Tuesday, October 11, 2016 at 7:47:47 PM UTC, John H Palmieri wrote:Right, Sage's Python is broken. Try deleting sage/local/bin/python and python2, and also sage/local/lib/python2.7 and sage/local/lib/libpython2.7.dylib. Then the build process should use the system's Python until Sage builds a working one.hmm, I don't understand. I think I tried starting from 'make distclean' and still got stuck at that No module named _scproxy thing.
Are you saying you did this with the 'develop' branch or with the branch from #21567? I can understand the former; that's why we have #21567.
When we build Python on OS X, we should test that _scproxy builds correctly before declaring the build a success.
Anne Schilling
Oct 11, 2016, 11:35:39 PM10/11/16
to sage-devel
Hi John,
Thank you for the answer! I did what you suggested and this time, sage started compiling and got to here:
....
[gf2x-1.1.p1] make[5]: Nothing to be done for `install-exec-am'.
[gf2x-1.1.p1] make[5]: Nothing to be done for `install-data-am'.
[gf2x-1.1.p1] Making install in src
[gf2x-1.1.p1] make install-am
[gf2x-1.1.p1] make[6]: Nothing to be done for `install-exec-am'.
[gf2x-1.1.p1] make[6]: Nothing to be done for `install-data-am'.
[gf2x-1.1.p1]
[gf2x-1.1.p1] real 4m35.653s
[gf2x-1.1.p1] user 4m21.480s
[gf2x-1.1.p1] sys 0m14.484s
[gf2x-1.1.p1] Successfully installed gf2x-1.1.p1
[gf2x-1.1.p1] Deleting temporary build directory
[gf2x-1.1.p1] /Applications/sage/local/var/tmp/sage/build/gf2x-1.1.p1
[gf2x-1.1.p1] Finished installing gf2x-1.1.p1.spkg
Thank you for the answer! I did what you suggested and this time, sage started compiling and got to here:
....
[gf2x-1.1.p1] make[5]: Nothing to be done for `install-exec-am'.
[gf2x-1.1.p1] make[5]: Nothing to be done for `install-data-am'.
[gf2x-1.1.p1] Making install in src
[gf2x-1.1.p1] make install-am
[gf2x-1.1.p1] make[6]: Nothing to be done for `install-exec-am'.
[gf2x-1.1.p1] make[6]: Nothing to be done for `install-data-am'.
[gf2x-1.1.p1]
[gf2x-1.1.p1] real 4m35.653s
[gf2x-1.1.p1] user 4m21.480s
[gf2x-1.1.p1] sys 0m14.484s
[gf2x-1.1.p1] Successfully installed gf2x-1.1.p1
[gf2x-1.1.p1] Deleting temporary build directory
[gf2x-1.1.p1] /Applications/sage/local/var/tmp/sage/build/gf2x-1.1.p1
[gf2x-1.1.p1] Finished installing gf2x-1.1.p1.spkg
make[1]: *** [all] Error 2
real 36m26.897s
user 95m0.211s
sys 12m51.527s
user 95m0.211s
sys 12m51.527s
***************************************************************
Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all'):
* package: givaro-4.0.2
log file: /Applications/sage/logs/pkgs/givaro-4.0.2.log
build directory: /Applications/sage/local/var/tmp/sage/build/givaro-4.0.2
log file: /Applications/sage/logs/pkgs/givaro-4.0.2.log
build directory: /Applications/sage/local/var/tmp/sage/build/givaro-4.0.2
The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
make: *** [all] Error 1
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
make: *** [all] Error 1
Any further ideas?
Anne
Anne
Anne Schilling
Oct 11, 2016, 11:41:29 PM10/11/16
to sage-devel
Wait, isn't this the error I started with before I upgraded to OSX 10.12 etc? I seem to be going in circles.
Is this related to https://trac.sagemath.org/ticket/17635?
Cheers,
Anne
Is this related to https://trac.sagemath.org/ticket/17635?
Cheers,
Anne
Francois Bissey
Oct 12, 2016, 12:18:22 AM10/12/16
to sage-...@googlegroups.com
Ok the initial problem was with avx instructions. Either givaro gets
misconfigured in thinking you have avx or someone you get a broken assembler.
Can you try
CXXFLAGS=“-Wa,-q” ./sage -i givaro
misconfigured in thinking you have avx or someone you get a broken assembler.
Can you try
CXXFLAGS=“-Wa,-q” ./sage -i givaro
Anne Schilling
Oct 12, 2016, 1:34:36 AM10/12/16
to sage-devel
I reinstalled all of XCode now (not just the command line version) and sage compiles again! Yippieh! Thank you all for your help!
Anne
Anne
Dima Pasechnik
Oct 12, 2016, 5:48:27 AM10/12/16
to sage-devel
I see, thanks. I should have been cc'ng myself on #21567 long ago.
Anyway, is it the time we open a meta-ticket on enabling full build of Sage with clang(++) ?
(and creating a gfortran package to deal with fortran)
It seems to be within reach nowadays.
Francois Bissey
Oct 12, 2016, 6:03:08 AM10/12/16
to sage-...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages