Sage is compiled with GCC. Can you enter a sage shell "sage -sh" and then try again the compilation, then that'll use the same compiler.
Also, your header search path should be something like: $ sage -sh Starting subshell with Sage environment variables set. Don't forget to exit when you are done. Beware: * Do not do anything with other copies of Sage on your system. * Do not use this for installing Sage packages using "sage -i" or for running "make" at Sage's root directory. These should be done outside the Sage shell. Bypassing shell configuration files... Note: SAGE_ROOT=/Users/vbraun/Sage $ cpp -v Using built-in specs. COLLECT_GCC=cpp Target: x86_64-apple-darwin14.0.0 Configured with: ../src/configure --prefix=/Users/vbraun/Sage/local --with-local-prefix=/Users/vbraun/Sage/local --with-gmp=/Users/vbraun/Sage/local --with-mpfr=/Users/vbraun/Sage/local --with-mpc=/Users/vbraun/Sage/local --with-system-zlib --disable-multilib --disable-nls --enable-languages=c,c++,fortran --disable-libitm --without-isl --without-cloog Thread model: posix gcc version 4.9.2 (GCC) COLLECT_GCC_OPTIONS='-E' '-mmacosx-version-min=10.9' '-v' '-mtune=core2' /Users/vbraun/Sage/local/libexec/gcc/x86_64-apple-darwin14.0.0/4.9.2/cc1 -E -quiet -v -D__DYNAMIC__ - -fPIC -mmacosx-version-min=10.9 -mtune=core2 ignoring nonexistent directory "/Users/vbraun/Sage/local/lib/gcc/x86_64-apple-darwin14.0.0/4.9.2/../../../../x86_64-apple-darwin14.0.0/include" ignoring duplicate directory "/Users/vbraun/Sage/local/include" as it is a non-system directory that duplicates a system directory #include "..." search starts here: #include <...> search starts here: /Users/vbraun/Sage/local/lib/gcc/x86_64-apple-darwin14.0.0/4.9.2/include /Users/vbraun/Sage/local/include /Users/vbraun/Sage/local/lib/gcc/x86_64-apple-darwin14.0.0/4.9.2/include-fixed /usr/include /System/Library/Frameworks /Library/Frameworks End of search list. ^C On Saturday, February 7, 2015 at 4:42:49 AM UTC+1, Xander Faber wrote: > > Hi Bill, > > Thanks for the detailed instructions. mpir-2.7.0 and mpfr-3.1.2 build > fine on my system. When I run the makefile for flint, I get the following > messages after a while: > > ` CC ../build/fq_zech_poly_factor/fq_zech_poly_factor_print.o > CC ../build/fq_zech_poly_factor/fq_zech_poly_factor_print_pretty.o > CC ../build/fq_zech_poly_factor/fq_zech_poly_factor_realloc.o > CC ../build/fq_zech_poly_factor/fq_zech_poly_factor_set.o > AR libflint.a > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: > > file: libflint.a(fq_zech_clear.o) has no symbols > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: > > file: libflint.a(fq_zech_clear.o) has no symbols > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: > > file: libflint.a(fq_zech_clear.o) has no symbols > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: > > file: libflint.a(fq_zech_clear.o) has no symbols > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: > > file: libflint.a(fq_zech_clear.o) has no symbols` > > It does, however, proceed beyond the point where Sage's flint compile > crashes. > > Afterward, I ran > > make check > > and everything passed. Soooo ... Sage specific problem, you're thinking? > Since I've now compiled mpir-2.70, mpfr-3.1.2, and flint-2.4.4 separately, > is it feasible to just copy these libraries into the Sage directory and > proceed with the Sage build? Any idea where I would put them? > > -Xander > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
