[sage-devel] Re: [sage-combinat-devel] Sage Days 65 mini report
On Saturday, June 13, 2015 at 2:05:54 PM UTC-4, Volker Braun wrote: On Saturday, June 13, 2015 at 1:27:30 AM UTC+2, William wrote: I'm also curious if anybody has any -- possibly *radical* -- suggestions about how to address this problem using new ideas. Use Docker (or boot2docker on OSX and Windows) to build and run Sage. Pro: Instant windows port. Boot2docker bundles VirtualBox. Kitematic installs boot2docker as part of its install, we could just copy that. Gives us a reproducable build environment with a guaranteed working toolchain. Con: Requires 64-bit and VT-x. Some Windows boxes still ship with VT-x disabled in the bios. A bit less efficient than native. I just tried this out on a 2011 imac and it worked very well. It was all very smooth. This is for the 6.7 release. How difficult would it be to automatically create a docker image for each development version? To do actual development, one would also want git, the git-trac command, a way to launch a terminal in the virtual machine (in general, a way to edit files). Can you update the README.md with hints on how to go about doing this? https://github.com/sagemath/docker Franco -- 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.
Re: [sage-combinat-devel] Sage Days 65 mini report
On Saturday, June 13, 2015 at 2:05:54 PM UTC-4, Volker Braun wrote: On Saturday, June 13, 2015 at 1:27:30 AM UTC+2, William wrote: I'm also curious if anybody has any -- possibly *radical* -- suggestions about how to address this problem using new ideas. Use Docker (or boot2docker on OSX and Windows) to build and run Sage. Pro: Instant windows port. Boot2docker bundles VirtualBox. Kitematic installs boot2docker as part of its install, we could just copy that. Gives us a reproducable build environment with a guaranteed working toolchain. Con: Requires 64-bit and VT-x. Some Windows boxes still ship with VT-x disabled in the bios. A bit less efficient than native. I just tried this out on a 2011 imac and it worked very well. It was all very smooth. This is for the 6.7 release. How difficult would it be to automatically create a docker image for each development version? To do actual development, one would also want git, the git-trac command, a way to launch a terminal in the virtual machine (in general, a way to edit files). Can you update the README.md with hints on how to go about doing this? https://github.com/sagemath/docker Franco -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Erreur with git while compiling sage on linux
Could you post the build log? Best, Travis On Thursday, June 18, 2015 at 4:00:10 PM UTC-7, Paul Mercat wrote: Hi ! I try to compile sage on linux, and I get the following error. Do you know what is the problem and how correct it ? . . . GEN perl/PM.stamp make[4]: Entering directory `/home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0/src/perl' /usr/bin/perl Makefile.PL PREFIX='/home/paul.mercat/sage/local' INSTALL_BASE='' --localedir='/home/paul.mercat/sage/local/share/locale' Can't locate ExtUtils/MakeMaker.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at Makefile.PL line 3. BEGIN failed--compilation aborted at Makefile.PL line 3. make[4]: *** [perl.mak] Error 2 make[4]: Leaving directory `/home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0/src/perl' make[3]: *** [perl/perl.mak] Error 2 make[3]: Leaving directory `/home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0/src' Error building git. real0m51.380s user0m38.300s sys 0m9.057s Error installing package git-2.3.0 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /home/paul.mercat/sage/logs/pkgs/git-2.3.0.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0 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 '/home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0' '/home/paul.mercat/sage/sage' --sh) When you are done debugging, you can type exit to leave the subshell. make[2]: *** [/home/paul.mercat/sage/local/var/lib/sage/installed/git-2.3.0] Error 1 make[2]: Leaving directory `/home/paul.mercat/sage/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/paul.mercat/sage/build' real389m1.753s user335m46.587s sys 34m2.341s *** Error building Sage. The following package(s) may have failed to build: package: git-2.3.0 log file: /home/paul.mercat/sage/logs/pkgs/git-2.3.0.log build directory: /home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0 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. -- 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.
Re: [sage-devel] Re: [sage-combinat-devel] Sage Days 65 mini report
Perhaps a slightly less radical idea would be to make sage interface with the underlying package manager to install the necessary dependencies when running make. Or at the very least, stop immediately and state what needs to be installed if a system-wide dependency is not available. Best, Travis On Thursday, June 18, 2015 at 3:08:57 PM UTC-7, la...@math.luc.edu wrote: I may be a example of Volker's random crap problem... I participated in sage days 65 and still don't have a sage-from-source compiled. (see separate note in sage-devel.) I also know next-to-nothing about make and computer architecture, so feel free to dismiss the following... How about this for a *radical* idea: a true bundle, with EVERYTHING that one needs all in the SAGE_ROOT directory. If you look at http://www.sagemath.org/documentation/html/en/installation/source.html you find the line Since Sage builds its own GCC if needed, So some version of what I suggest supposedly already happens. (btw, I would *love* for that to happen on my machine, and make, and m4 and perl and ... as I suspect things are really out-of-whack for me right now.) If so, one needn't hope that things are installed correctly on a given machine, because everything starts from SAGE_ROOT. -- 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.
[sage-devel] Re: Error compiling MPFR on development version install
Okay... I am now running 10.10.3. to try to get a clean version of tools, I deleted the following three directories: * /Applications/Xcode.app * /Library/Developer/CommandLineTools * /usr/include/c++ I ran xcode-select --install from the command line. A pop up asked me to install. I did. Now /Library/Developer/CommandLineTools and /usr/include/c++ have returned. (note that I do not have XCode.app at present) Still, in my sage source directory, when I run make -j4, I get errors. (Setting SAGE_KEEP_BUILT_SPKGS='yes' doesn't eliminate the problem.) There are errors in the packages *mpfr-3.1.2.p0* and *zlib-1.2.8.p0*. In my logs, the packages seem not to be able to find files that I'm sure are there: *float.h* and *stdarg.h* indeed, there is some general checks that flew by earlier in the build process to the effect, checking float.h usability... yes checking float.h presence... yes checking for float.h... yes Yet, mpfr cannot find it. Similarly, earlier in the 'make' process, I saw fly by the line checking whether stdarg.h exists and works... yes new output of gcc --version : Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) Target: x86_64-apple-darwin14.3.0 Thread model: posix (note: both of the directories mentioned do exist. The files *float.h* and *stdarg.h* exist in: * /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/ * /usr/include/c++/4.2.1/tr1/ among other places) output of xcode-select --version : xcode-select version 2333 output of locate stdarg.h : /Applications/local/include/c++/4.6.3/tr1/stdarg.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/cross-stdarg.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/stdarg.h /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Clang/include/stdarg.h /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/stdarg.h /Library/Developer/CommandLineTools/usr/lib/llvm-gcc/4.2.1/include/stdarg.h /System/Library/Frameworks/Kernel.framework/Versions/A/Headers/stdarg.h /System/Library/Frameworks/OpenCL.framework/Versions/A/lib/clang/2.0/include/stdarg.h /usr/include/c++/4.2.1/tr1/stdarg.h output of locate float.h : /Applications/gap4r4/src/float.h /Applications/local/include/c++/4.6.3/tr1/float.h /Applications/local/lib/gap-4.4.12/src/float.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/float.h /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Clang/include/float.h /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/float.h /System/Library/Frameworks/OpenCL.framework/Versions/A/lib/clang/2.0/include/float.h /usr/include/c++/4.2.1/tr1/float.h Any further ideas? On Wednesday, June 10, 2015 at 2:56:55 PM UTC-5, Volker Braun wrote: Since Apple declined to fix the rootpipe bug in OSX 10.9 I would recommend to upgrade to OSX 10.10 asap, effectively you don't receive security fixes any more. Even then, why did you not upgrade to command line tools 6.2? They should still run on OSX 10.9 On Wednesday, June 10, 2015 at 7:43:14 PM UTC+2, la...@math.luc.edu wrote: Volkar: Here's more info: weehawken:sage-git lauve$ gcc --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn) Target: x86_64-apple-darwin13.4.0 Thread model: posix weehawken:sage-git lauve$ which gcc /usr/bin/gcc Note: the 'prefix' it points to is not where I have installed the most recent version of command line tools, but I moved the 'usr' folder there to 'usr.old', created a symbolic link to '/usr' and tried again. The error persists: float.h not found On Wednesday, June 10, 2015 at 10:32:30 AM UTC-5, Volker Braun wrote: CommandLineTools for XCode 6.1.1 is old and buggy... Also, are you sure you are using the compiler you think you are using? You can have multiple ones. Output of gcc --version? On Wednesday, June 10, 2015 at 4:37:13 PM UTC+2, Anne Schilling wrote: Hello, Aaron Lauve at Sage Days 65 is having trouble installing development version of Sage on my Mac. (OSX10.9.5, with CommandLineTools for XCode 6.1.1 installed) The error is Error installing package mpfr-3.1.2.p0 Here is the tail of the log file created, which seems to point to not finding float.h (But it can be located on my machine with locate float.h from / directory.) ~~~ checking for limits.h... yes checking float.h usability... no checking float.h presence... no checking for float.h... no configure: error: float.h not found Error configuring MPFR. See above for the options passed to it, and the file
[sage-devel] Re: Error compiling MPFR on development version install
will install Xcode and get back to you. in the meantime, did you just want a directory listing, or the actual logs? weehawken:sage-devel lauve$ ls logs/pkgs/ bzip2-1.0.6.20140317.log mpfr-3.1.2.p0.logpkgconf-0.9.7.log config.log mpir-2.7.0-alpha12.log zlib-1.2.8.p0.log iconv-1.14.log patch-2.7.1.log On Thursday, June 18, 2015 at 1:27:43 PM UTC-5, Volker Braun wrote: I think you need to have XCode installed, even though you shouldn't have to. Can you also post logs (in SAGE_ROOT/logs/pkgs/) On Thursday, June 18, 2015 at 7:29:56 PM UTC+2, la...@math.luc.edu wrote: Okay... I am now running 10.10.3. to try to get a clean version of tools, I deleted the following three directories: * /Applications/Xcode.app * /Library/Developer/CommandLineTools * /usr/include/c++ I ran xcode-select --install from the command line. A pop up asked me to install. I did. Now /Library/Developer/CommandLineTools and /usr/include/c++ have returned. (note that I do not have XCode.app at present) Still, in my sage source directory, when I run make -j4, I get errors. (Setting SAGE_KEEP_BUILT_SPKGS='yes' doesn't eliminate the problem.) There are errors in the packages *mpfr-3.1.2.p0* and *zlib-1.2.8.p0*. In my logs, the packages seem not to be able to find files that I'm sure are there: *float.h* and *stdarg.h* indeed, there is some general checks that flew by earlier in the build process to the effect, checking float.h usability... yes checking float.h presence... yes checking for float.h... yes Yet, mpfr cannot find it. Similarly, earlier in the 'make' process, I saw fly by the line checking whether stdarg.h exists and works... yes new output of gcc --version : Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) Target: x86_64-apple-darwin14.3.0 Thread model: posix (note: both of the directories mentioned do exist. The files *float.h* and *stdarg.h* exist in: * /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/ * /usr/include/c++/4.2.1/tr1/ among other places) output of xcode-select --version : xcode-select version 2333 output of locate stdarg.h : /Applications/local/include/c++/4.6.3/tr1/stdarg.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/cross-stdarg.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/stdarg.h /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Clang/include/stdarg.h /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/stdarg.h /Library/Developer/CommandLineTools/usr/lib/llvm-gcc/4.2.1/include/stdarg.h /System/Library/Frameworks/Kernel.framework/Versions/A/Headers/stdarg.h /System/Library/Frameworks/OpenCL.framework/Versions/A/lib/clang/2.0/include/stdarg.h /usr/include/c++/4.2.1/tr1/stdarg.h output of locate float.h : /Applications/gap4r4/src/float.h /Applications/local/include/c++/4.6.3/tr1/float.h /Applications/local/lib/gap-4.4.12/src/float.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/float.h /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Clang/include/float.h /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/float.h /System/Library/Frameworks/OpenCL.framework/Versions/A/lib/clang/2.0/include/float.h /usr/include/c++/4.2.1/tr1/float.h Any further ideas? On Wednesday, June 10, 2015 at 2:56:55 PM UTC-5, Volker Braun wrote: Since Apple declined to fix the rootpipe bug in OSX 10.9 I would recommend to upgrade to OSX 10.10 asap, effectively you don't receive security fixes any more. Even then, why did you not upgrade to command line tools 6.2? They should still run on OSX 10.9 On Wednesday, June 10, 2015 at 7:43:14 PM UTC+2, la...@math.luc.edu wrote: Volkar: Here's more info: weehawken:sage-git lauve$ gcc --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn) Target: x86_64-apple-darwin13.4.0 Thread model: posix weehawken:sage-git lauve$ which gcc /usr/bin/gcc Note: the 'prefix' it points to is not where I have installed the most recent version of command line tools, but I moved the 'usr' folder there to 'usr.old', created a symbolic link to '/usr' and tried again. The error persists: float.h not found On Wednesday, June 10, 2015 at 10:32:30 AM UTC-5, Volker Braun wrote: CommandLineTools for XCode 6.1.1 is old and buggy... Also, are you sure you are using the compiler you think you are using? You can have multiple ones. Output of gcc --version? On Wednesday, June 10, 2015 at 4:37:13 PM UTC+2, Anne
[sage-devel] Re: Error compiling MPFR on development version install
I think you need to have XCode installed, even though you shouldn't have to. Can you also post logs (in SAGE_ROOT/logs/pkgs/) On Thursday, June 18, 2015 at 7:29:56 PM UTC+2, la...@math.luc.edu wrote: Okay... I am now running 10.10.3. to try to get a clean version of tools, I deleted the following three directories: * /Applications/Xcode.app * /Library/Developer/CommandLineTools * /usr/include/c++ I ran xcode-select --install from the command line. A pop up asked me to install. I did. Now /Library/Developer/CommandLineTools and /usr/include/c++ have returned. (note that I do not have XCode.app at present) Still, in my sage source directory, when I run make -j4, I get errors. (Setting SAGE_KEEP_BUILT_SPKGS='yes' doesn't eliminate the problem.) There are errors in the packages *mpfr-3.1.2.p0* and *zlib-1.2.8.p0*. In my logs, the packages seem not to be able to find files that I'm sure are there: *float.h* and *stdarg.h* indeed, there is some general checks that flew by earlier in the build process to the effect, checking float.h usability... yes checking float.h presence... yes checking for float.h... yes Yet, mpfr cannot find it. Similarly, earlier in the 'make' process, I saw fly by the line checking whether stdarg.h exists and works... yes new output of gcc --version : Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) Target: x86_64-apple-darwin14.3.0 Thread model: posix (note: both of the directories mentioned do exist. The files *float.h* and *stdarg.h* exist in: * /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/ * /usr/include/c++/4.2.1/tr1/ among other places) output of xcode-select --version : xcode-select version 2333 output of locate stdarg.h : /Applications/local/include/c++/4.6.3/tr1/stdarg.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/cross-stdarg.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/stdarg.h /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Clang/include/stdarg.h /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/stdarg.h /Library/Developer/CommandLineTools/usr/lib/llvm-gcc/4.2.1/include/stdarg.h /System/Library/Frameworks/Kernel.framework/Versions/A/Headers/stdarg.h /System/Library/Frameworks/OpenCL.framework/Versions/A/lib/clang/2.0/include/stdarg.h /usr/include/c++/4.2.1/tr1/stdarg.h output of locate float.h : /Applications/gap4r4/src/float.h /Applications/local/include/c++/4.6.3/tr1/float.h /Applications/local/lib/gap-4.4.12/src/float.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/float.h /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Clang/include/float.h /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/float.h /System/Library/Frameworks/OpenCL.framework/Versions/A/lib/clang/2.0/include/float.h /usr/include/c++/4.2.1/tr1/float.h Any further ideas? On Wednesday, June 10, 2015 at 2:56:55 PM UTC-5, Volker Braun wrote: Since Apple declined to fix the rootpipe bug in OSX 10.9 I would recommend to upgrade to OSX 10.10 asap, effectively you don't receive security fixes any more. Even then, why did you not upgrade to command line tools 6.2? They should still run on OSX 10.9 On Wednesday, June 10, 2015 at 7:43:14 PM UTC+2, la...@math.luc.edu wrote: Volkar: Here's more info: weehawken:sage-git lauve$ gcc --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn) Target: x86_64-apple-darwin13.4.0 Thread model: posix weehawken:sage-git lauve$ which gcc /usr/bin/gcc Note: the 'prefix' it points to is not where I have installed the most recent version of command line tools, but I moved the 'usr' folder there to 'usr.old', created a symbolic link to '/usr' and tried again. The error persists: float.h not found On Wednesday, June 10, 2015 at 10:32:30 AM UTC-5, Volker Braun wrote: CommandLineTools for XCode 6.1.1 is old and buggy... Also, are you sure you are using the compiler you think you are using? You can have multiple ones. Output of gcc --version? On Wednesday, June 10, 2015 at 4:37:13 PM UTC+2, Anne Schilling wrote: Hello, Aaron Lauve at Sage Days 65 is having trouble installing development version of Sage on my Mac. (OSX10.9.5, with CommandLineTools for XCode 6.1.1 installed) The error is Error installing package mpfr-3.1.2.p0 Here is the tail of the log file created, which seems to point to not finding float.h (But it can be located on my machine with locate float.h from / directory.) ~~~
Re: [sage-devel] The future of polybori
Right, we started with boost-python to have a language to play with. There was no standalone cython in the first and c++ had not been so well supported by cython then. So, boost was the rapid way to get a small OSS with few dependencies. However, the middle-end ;-) is flexible, so the bindings could easily be replaced, which had been done for Sage then. Partially to avoid shipping boost-python and for performace reasons as far as I recall. Nowadays a fork could soley rely on cython, I guess. -- 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.
[sage-devel] Re: Error compiling MPFR on development version install
The actual logs of whatever failed On Thursday, June 18, 2015 at 8:56:56 PM UTC+2, la...@math.luc.edu wrote: will install Xcode and get back to you. in the meantime, did you just want a directory listing, or the actual logs? weehawken:sage-devel lauve$ ls logs/pkgs/ bzip2-1.0.6.20140317.log mpfr-3.1.2.p0.logpkgconf-0.9.7.log config.log mpir-2.7.0-alpha12.log zlib-1.2.8.p0.log iconv-1.14.log patch-2.7.1.log On Thursday, June 18, 2015 at 1:27:43 PM UTC-5, Volker Braun wrote: I think you need to have XCode installed, even though you shouldn't have to. Can you also post logs (in SAGE_ROOT/logs/pkgs/) On Thursday, June 18, 2015 at 7:29:56 PM UTC+2, la...@math.luc.edu wrote: Okay... I am now running 10.10.3. to try to get a clean version of tools, I deleted the following three directories: * /Applications/Xcode.app * /Library/Developer/CommandLineTools * /usr/include/c++ I ran xcode-select --install from the command line. A pop up asked me to install. I did. Now /Library/Developer/CommandLineTools and /usr/include/c++ have returned. (note that I do not have XCode.app at present) Still, in my sage source directory, when I run make -j4, I get errors. (Setting SAGE_KEEP_BUILT_SPKGS='yes' doesn't eliminate the problem.) There are errors in the packages *mpfr-3.1.2.p0* and *zlib-1.2.8.p0*. In my logs, the packages seem not to be able to find files that I'm sure are there: *float.h* and *stdarg.h* indeed, there is some general checks that flew by earlier in the build process to the effect, checking float.h usability... yes checking float.h presence... yes checking for float.h... yes Yet, mpfr cannot find it. Similarly, earlier in the 'make' process, I saw fly by the line checking whether stdarg.h exists and works... yes new output of gcc --version : Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) Target: x86_64-apple-darwin14.3.0 Thread model: posix (note: both of the directories mentioned do exist. The files *float.h* and *stdarg.h* exist in: * /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/ * /usr/include/c++/4.2.1/tr1/ among other places) output of xcode-select --version : xcode-select version 2333 output of locate stdarg.h : /Applications/local/include/c++/4.6.3/tr1/stdarg.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/cross-stdarg.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/stdarg.h /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Clang/include/stdarg.h /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/stdarg.h /Library/Developer/CommandLineTools/usr/lib/llvm-gcc/4.2.1/include/stdarg.h /System/Library/Frameworks/Kernel.framework/Versions/A/Headers/stdarg.h /System/Library/Frameworks/OpenCL.framework/Versions/A/lib/clang/2.0/include/stdarg.h /usr/include/c++/4.2.1/tr1/stdarg.h output of locate float.h : /Applications/gap4r4/src/float.h /Applications/local/include/c++/4.6.3/tr1/float.h /Applications/local/lib/gap-4.4.12/src/float.h /Applications/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include/float.h /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Clang/include/float.h /Library/Developer/CommandLineTools/usr/lib/clang/6.1.0/include/float.h /System/Library/Frameworks/OpenCL.framework/Versions/A/lib/clang/2.0/include/float.h /usr/include/c++/4.2.1/tr1/float.h Any further ideas? On Wednesday, June 10, 2015 at 2:56:55 PM UTC-5, Volker Braun wrote: Since Apple declined to fix the rootpipe bug in OSX 10.9 I would recommend to upgrade to OSX 10.10 asap, effectively you don't receive security fixes any more. Even then, why did you not upgrade to command line tools 6.2? They should still run on OSX 10.9 On Wednesday, June 10, 2015 at 7:43:14 PM UTC+2, la...@math.luc.edu wrote: Volkar: Here's more info: weehawken:sage-git lauve$ gcc --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn) Target: x86_64-apple-darwin13.4.0 Thread model: posix weehawken:sage-git lauve$ which gcc /usr/bin/gcc Note: the 'prefix' it points to is not where I have installed the most recent version of command line tools, but I moved the 'usr' folder there to 'usr.old', created a symbolic link to '/usr' and tried again. The error persists: float.h not found On Wednesday, June 10, 2015 at 10:32:30 AM UTC-5, Volker Braun wrote: CommandLineTools for XCode 6.1.1 is old and buggy... Also, are you sure you are using the compiler you think you are using?
[sage-devel] Re: Error compiling MPFR on development version install
Re: possibly needing to install Xcode: I installed it. restarted machine. ran 'make distclean' then ran 'make'. Same problem. two files (float.h and stdarg.h) that cannot be found, though they exist. 'xcode-select --version' and 'gcc --version' return the same output as I mentioned before. Here are the logs, in full. ~~~ ~~~ mpfr ~~ Found local metadata for mpfr-3.1.2.p0 Found local sources at /Users/lauve/sage-devel/upstream/mpfr-3.1.2.tar.bz2 Checksum: e70341aa7974b4ba1023c75c750aca68222b0723 vs e70341aa7974b4ba1023c75c750aca68222b0723 mpfr-3.1.2.p0 Setting up build directory for mpfr-3.1.2.p0 Finished set up Host system: Darwin weehawken.local 14.3.0 Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64 x86_64 C compiler: /usr/bin/clang C compiler version: Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) Target: x86_64-apple-darwin14.3.0 Thread model: posix Patching MPFR... Now configuring MPFR... Checking what CC and CFLAGS MPFR would use if they were empty... Settings chosen by MPFR when configuring with CC and CFLAGS unset: CC: /usr/bin/gcc CFLAGS: -Wall -Wmissing-prototypes -Wpointer-arith -m64 -O2 -march=corei7-avx -mtune=corei7-avx -g Settings required to properly build MPFR, taking into account SAGE_DEBUG etc.: CFLAGS: LDFLAGS: ABI: Settings from the global environment: CC: /usr/bin/clang CFLAGS: (CPPFLAGS, CXX and CXXFLAGS are listed below; these don't get modified.) Using MPFR's settings (plus mandatory ones). Finally using the following settings: CC=/usr/bin/clang CFLAGS=-Wall -Wmissing-prototypes -Wpointer-arith -m64 -O2 -march=corei7-avx -mtune=corei7-avx -g CPP= CPPFLAGS= CXX=/usr/bin/clang++ CXXFLAGS= LDFLAGS= ABI= (These settings may still get overridden by 'configure' or Makefiles.) Configuring MPFR with the following options: --prefix=/Users/lauve/sage-devel/local --libdir=/Users/lauve/sage-devel/local/lib --with-gmp=/Users/lauve/sage-devel/local --disable-thread-safe You can set MPFR_CONFIGURE to pass additional parameters. checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./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 to enable maintainer-specific portions of Makefiles... yes checking build system type... x86_64-apple-darwin14.3.0 checking host system type... x86_64-apple-darwin14.3.0 checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for a sed that does not truncate output... /usr/bin/sed checking for gcc... /usr/bin/clang 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 /usr/bin/clang accepts -g... yes checking for /usr/bin/clang option to accept ISO C89... unsupported checking for style of include used by make... GNU checking dependency style of /usr/bin/clang... gcc3 checking how to run the C preprocessor... /usr/bin/clang -E checking for ICC... no checking whether /usr/bin/clang and cc understand -c and -o together... rm: conftest.dSYM: is a directory yes checking if the compiler understands -Wl,-search_paths_first... yes checking for an ANSI C-conforming const... yes checking for working volatile... yes checking for main in -lm... yes checking whether time.h and sys/time.h may both be included... yes checking for ANSI C header files... no 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 size_t... yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking float.h usability... no checking float.h presence... no checking for float.h... no configure: error: float.h not found Error configuring MPFR. See above for the options passed to it, and the file /Users/lauve/sage-devel/local/var/tmp/sage/build/mpfr-3.1.2.p0/src/config.log for details. real 0m26.664s user 0m10.775s sys 0m9.652s Error installing package mpfr-3.1.2.p0 Please email sage-devel
Re: [sage-devel] Error compiling MPFR on development version install
That file please: /Users/lauve/sage-devel/local/var/tmp/sage/build/mpfr-3.1.2.p0/src/config.log On 19/06/2015, at 08:43, la...@math.luc.edu wrote: Re: possibly needing to install Xcode: I installed it. restarted machine. ran 'make distclean' then ran 'make'. Same problem. two files (float.h and stdarg.h) that cannot be found, though they exist. 'xcode-select --version' and 'gcc --version' return the same output as I mentioned before. Here are the logs, in full. ~~~ ~~~ mpfr ~~ Found local metadata for mpfr-3.1.2.p0 Found local sources at /Users/lauve/sage-devel/upstream/mpfr-3.1.2.tar.bz2 Checksum: e70341aa7974b4ba1023c75c750aca68222b0723 vs e70341aa7974b4ba1023c75c750aca68222b0723 mpfr-3.1.2.p0 Setting up build directory for mpfr-3.1.2.p0 Finished set up Host system: Darwin weehawken.local 14.3.0 Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64 x86_64 C compiler: /usr/bin/clang C compiler version: Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) Target: x86_64-apple-darwin14.3.0 Thread model: posix Patching MPFR... Now configuring MPFR... Checking what CC and CFLAGS MPFR would use if they were empty... Settings chosen by MPFR when configuring with CC and CFLAGS unset: CC: /usr/bin/gcc CFLAGS: -Wall -Wmissing-prototypes -Wpointer-arith -m64 -O2 -march=corei7-avx -mtune=corei7-avx -g Settings required to properly build MPFR, taking into account SAGE_DEBUG etc.: CFLAGS: LDFLAGS: ABI: Settings from the global environment: CC: /usr/bin/clang CFLAGS: (CPPFLAGS, CXX and CXXFLAGS are listed below; these don't get modified.) Using MPFR's settings (plus mandatory ones). Finally using the following settings: CC=/usr/bin/clang CFLAGS=-Wall -Wmissing-prototypes -Wpointer-arith -m64 -O2 -march=corei7-avx -mtune=corei7-avx -g CPP= CPPFLAGS= CXX=/usr/bin/clang++ CXXFLAGS= LDFLAGS= ABI= (These settings may still get overridden by 'configure' or Makefiles.) Configuring MPFR with the following options: --prefix=/Users/lauve/sage-devel/local --libdir=/Users/lauve/sage-devel/local/lib --with-gmp=/Users/lauve/sage-devel/local --disable-thread-safe You can set MPFR_CONFIGURE to pass additional parameters. checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./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 to enable maintainer-specific portions of Makefiles... yes checking build system type... x86_64-apple-darwin14.3.0 checking host system type... x86_64-apple-darwin14.3.0 checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for a sed that does not truncate output... /usr/bin/sed checking for gcc... /usr/bin/clang 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 /usr/bin/clang accepts -g... yes checking for /usr/bin/clang option to accept ISO C89... unsupported checking for style of include used by make... GNU checking dependency style of /usr/bin/clang... gcc3 checking how to run the C preprocessor... /usr/bin/clang -E checking for ICC... no checking whether /usr/bin/clang and cc understand -c and -o together... rm: conftest.dSYM: is a directory yes checking if the compiler understands -Wl,-search_paths_first... yes checking for an ANSI C-conforming const... yes checking for working volatile... yes checking for main in -lm... yes checking whether time.h and sys/time.h may both be included... yes checking for ANSI C header files... no 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 size_t... yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking float.h usability... no checking float.h presence... no checking for float.h... no configure: error: float.h not found Error configuring MPFR. See above for the options passed to it, and the file /Users/lauve/sage-devel/local/var/tmp/sage/build/mpfr-3.1.2.p0/src/config.log for
[sage-devel] Re: Error compiling MPFR on development version install
There is something fishy even before the failure when I diff it with my log (see below): Your clang doesn't support C89 and misses ANSI C headers. Do you have anything in /usr/local installed? @@ -70,7 +71,7 @@ checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/clang accepts -g... yes -checking for /usr/bin/clang option to accept ISO C89... none needed +checking for /usr/bin/clang option to accept ISO C89... unsupported checking for style of include used by make... GNU checking dependency style of /usr/bin/clang... gcc3 checking how to run the C preprocessor... /usr/bin/clang -E @@ -82,7 +83,7 @@ checking for working volatile... yes checking for main in -lm... yes checking whether time.h and sys/time.h may both be included... yes -checking for ANSI C header files... yes +checking for ANSI C header files... no checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes @@ -95,2236 +96,6 @@ checking for size_t... yes checking limits.h usability... yes checking limits.h presence... yes -checking for limits.h... yes -checking float.h usability... yes -checking float.h presence... yes On Thursday, June 18, 2015 at 10:43:10 PM UTC+2, la...@math.luc.edu wrote: Re: possibly needing to install Xcode: I installed it. restarted machine. ran 'make distclean' then ran 'make'. Same problem. two files (float.h and stdarg.h) that cannot be found, though they exist. 'xcode-select --version' and 'gcc --version' return the same output as I mentioned before. Here are the logs, in full. ~~~ ~~~ mpfr ~~ Found local metadata for mpfr-3.1.2.p0 Found local sources at /Users/lauve/sage-devel/upstream/mpfr-3.1.2.tar.bz2 Checksum: e70341aa7974b4ba1023c75c750aca68222b0723 vs e70341aa7974b4ba1023c75c750aca68222b0723 mpfr-3.1.2.p0 Setting up build directory for mpfr-3.1.2.p0 Finished set up Host system: Darwin weehawken.local 14.3.0 Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64 x86_64 C compiler: /usr/bin/clang C compiler version: Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) Target: x86_64-apple-darwin14.3.0 Thread model: posix Patching MPFR... Now configuring MPFR... Checking what CC and CFLAGS MPFR would use if they were empty... Settings chosen by MPFR when configuring with CC and CFLAGS unset: CC: /usr/bin/gcc CFLAGS: -Wall -Wmissing-prototypes -Wpointer-arith -m64 -O2 -march=corei7-avx -mtune=corei7-avx -g Settings required to properly build MPFR, taking into account SAGE_DEBUG etc.: CFLAGS: LDFLAGS: ABI: Settings from the global environment: CC: /usr/bin/clang CFLAGS: (CPPFLAGS, CXX and CXXFLAGS are listed below; these don't get modified.) Using MPFR's settings (plus mandatory ones). Finally using the following settings: CC=/usr/bin/clang CFLAGS=-Wall -Wmissing-prototypes -Wpointer-arith -m64 -O2 -march=corei7-avx -mtune=corei7-avx -g CPP= CPPFLAGS= CXX=/usr/bin/clang++ CXXFLAGS= LDFLAGS= ABI= (These settings may still get overridden by 'configure' or Makefiles.) Configuring MPFR with the following options: --prefix=/Users/lauve/sage-devel/local --libdir=/Users/lauve/sage-devel/local/lib --with-gmp=/Users/lauve/sage-devel/local --disable-thread-safe You can set MPFR_CONFIGURE to pass additional parameters. checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./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 to enable maintainer-specific portions of Makefiles... yes checking build system type... x86_64-apple-darwin14.3.0 checking host system type... x86_64-apple-darwin14.3.0 checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for a sed that does not truncate output... /usr/bin/sed checking for gcc... /usr/bin/clang 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 /usr/bin/clang accepts -g... yes checking for /usr/bin/clang option to accept ISO C89... unsupported checking for style of include used by make... GNU checking dependency style of /usr/bin/clang... gcc3 checking how to run the C preprocessor...
Re: [sage-devel] Error compiling MPFR on development version install
Also, whats the header search path? Output of clang++ -E -x c++ - -v /dev/null -- 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.
[sage-devel] Erreur with git while compiling sage on linux
Hi ! I try to compile sage on linux, and I get the following error. Do you know what is the problem and how correct it ? . . . GEN perl/PM.stamp make[4]: Entering directory `/home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0/src/perl' /usr/bin/perl Makefile.PL PREFIX='/home/paul.mercat/sage/local' INSTALL_BASE='' --localedir='/home/paul.mercat/sage/local/share/locale' Can't locate ExtUtils/MakeMaker.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at Makefile.PL line 3. BEGIN failed--compilation aborted at Makefile.PL line 3. make[4]: *** [perl.mak] Error 2 make[4]: Leaving directory `/home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0/src/perl' make[3]: *** [perl/perl.mak] Error 2 make[3]: Leaving directory `/home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0/src' Error building git. real0m51.380s user0m38.300s sys 0m9.057s Error installing package git-2.3.0 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /home/paul.mercat/sage/logs/pkgs/git-2.3.0.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0 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 '/home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0' '/home/paul.mercat/sage/sage' --sh) When you are done debugging, you can type exit to leave the subshell. make[2]: *** [/home/paul.mercat/sage/local/var/lib/sage/installed/git-2.3.0] Error 1 make[2]: Leaving directory `/home/paul.mercat/sage/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/paul.mercat/sage/build' real389m1.753s user335m46.587s sys 34m2.341s *** Error building Sage. The following package(s) may have failed to build: package: git-2.3.0 log file: /home/paul.mercat/sage/logs/pkgs/git-2.3.0.log build directory: /home/paul.mercat/sage/local/var/tmp/sage/build/git-2.3.0 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. -- 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.
Re: [sage-devel] Re: [sage-combinat-devel] Sage Days 65 mini report
I may be a example of Volker's random crap problem... I participated in sage days 65 and still don't have a sage-from-source compiled. (see separate note in sage-devel.) I also know next-to-nothing about make and computer architecture, so feel free to dismiss the following... How about this for a *radical* idea: a true bundle, with EVERYTHING that one needs all in the SAGE_ROOT directory. If you look at http://www.sagemath.org/documentation/html/en/installation/source.html you find the line Since Sage builds its own GCC if needed, So some version of what I suggest supposedly already happens. (btw, I would *love* for that to happen on my machine, and make, and m4 and perl and ... as I suspect things are really out-of-whack for me right now.) If so, one needn't hope that things are installed correctly on a given machine, because everything starts from SAGE_ROOT. On Sunday, June 14, 2015 at 4:00:05 PM UTC-5, Jeroen Demeyer wrote: On 2015-06-14 11:05, Volker Braun wrote: But more machines won't help unless you want to install random crap on them. I don't know if you're serious, but I think that more machines *with* random crap might actually be a good idea. Normally, packages aren't supposed to look in /usr/local if they are passed proper configuration flags. If they still do, that's either a bug in the package or in the way we use it. -- 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.
[sage-devel] Re: Shortest expressions in permutation groups with generators
GAP4 has 39.5-2 Factorization (http://www.gap-system.org/Manuals/doc/ref/chap39.html) calling GAP from Sage is not hard... On Tuesday, 16 June 2015 17:02:35 UTC+1, Christian Stump wrote: Hi there, I wasn't able to find the following functionality: Let W = PermutationGroup(gens) be a permutation group and let w in W. Find a *shortest* expression as a group of w as a word in gens and their inverses. w.word_problem() finds a word, but this has not necessarily the shortest possible length. In GAP3 there was such a functionality which I currently use. * Is there already such functionality in Sage (and I was simply ignorant)? * Does anyone know how to achieve this using Sage and GAP4? * Should I open a ticket and provide GAP3 code for this functionality for permutation groups? Thanks! Christian -- 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.
[sage-devel] Re: Error compiling MPFR on development version install
On Thursday, June 18, 2015 at 5:30:14 PM UTC-5, Volker Braun wrote: There is something fishy even before the failure when I diff it with my log (see below): Your clang doesn't support C89 and misses ANSI C headers. Do you have anything in /usr/local installed? lots. e.g., 'texlive' and 'mysql' directories. in 'bin' one finds ps2pdf, etc. in 'include' one finds graphviz and aspell.h (i seem to be using the texlive. 'which latex' points to /usr/texbin/latex, but tracing down the symbolic links, it comes back to this texlive directory.) I will answer the other question from your other post here... weehawken:sage-devel lauve$ clang++ -E -x c++ - -v /dev/null Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) Target: x86_64-apple-darwin14.3.0 Thread model: posix /usr/bin/clang++ -cc1 -triple x86_64-apple-macosx10.10.0 -E -disable-free -disable-llvm-verifier -main-file-name - -mrelocation-model pic -pic-level 2 -mdisable-fp-elim -masm-verbose -munwind-tables -target-cpu core2 -target-linker-version 242 -v -dwarf-column-info -resource-dir /usr/bin/../lib/clang/6.1.0 -stdlib=libc++ -fdeprecated-macro -fdebug-compilation-dir /Users/lauve/sage-devel -ferror-limit 19 -fmessage-length 122 -stack-protector 1 -mstackrealign -fblocks -fobjc-runtime=macosx-10.10.0 -fencode-extended-block-signature -fcxx-exceptions -fexceptions -fmax-type-align=16 -fdiagnostics-show-option -fcolor-diagnostics -o - -x c++ - clang -cc1 version 6.1.0 based upon LLVM 3.6.0svn default target x86_64-apple-darwin14.3.0 ignoring nonexistent directory /usr/bin/../include/c++/v1 ignoring nonexistent directory /usr/include/c++/v1 ignoring nonexistent directory /usr/bin/../lib/clang/6.1.0/include #include ... search starts here: #include ... search starts here: /usr/local/include /usr/include /System/Library/Frameworks (framework directory) /Library/Frameworks (framework directory) End of search list. # 1 stdin # 1 built-in 1 # 1 built-in 3 # 326 built-in 3 # 1 command line 1 # 1 built-in 2 # 1 stdin 2 @@ -70,7 +71,7 @@ checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/clang accepts -g... yes -checking for /usr/bin/clang option to accept ISO C89... none needed +checking for /usr/bin/clang option to accept ISO C89... unsupported checking for style of include used by make... GNU checking dependency style of /usr/bin/clang... gcc3 checking how to run the C preprocessor... /usr/bin/clang -E @@ -82,7 +83,7 @@ checking for working volatile... yes checking for main in -lm... yes checking whether time.h and sys/time.h may both be included... yes -checking for ANSI C header files... yes +checking for ANSI C header files... no checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes @@ -95,2236 +96,6 @@ checking for size_t... yes checking limits.h usability... yes checking limits.h presence... yes -checking for limits.h... yes -checking float.h usability... yes -checking float.h presence... yes On Thursday, June 18, 2015 at 10:43:10 PM UTC+2, la...@math.luc.edu wrote: Re: possibly needing to install Xcode: I installed it. restarted machine. ran 'make distclean' then ran 'make'. Same problem. two files (float.h and stdarg.h) that cannot be found, though they exist. 'xcode-select --version' and 'gcc --version' return the same output as I mentioned before. Here are the logs, in full. ~~~ ~~~ mpfr ~~ Found local metadata for mpfr-3.1.2.p0 Found local sources at /Users/lauve/sage-devel/upstream/mpfr-3.1.2.tar.bz2 Checksum: e70341aa7974b4ba1023c75c750aca68222b0723 vs e70341aa7974b4ba1023c75c750aca68222b0723 mpfr-3.1.2.p0 Setting up build directory for mpfr-3.1.2.p0 Finished set up Host system: Darwin weehawken.local 14.3.0 Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64 x86_64 C compiler: /usr/bin/clang C compiler version: Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) Target: x86_64-apple-darwin14.3.0 Thread model: posix Patching MPFR... Now configuring MPFR... Checking what CC and CFLAGS MPFR would use if they were empty... Settings chosen by MPFR when configuring with CC and CFLAGS unset: CC: /usr/bin/gcc CFLAGS: -Wall -Wmissing-prototypes -Wpointer-arith -m64 -O2 -march=corei7-avx -mtune=corei7-avx -g Settings required to properly build MPFR, taking into account SAGE_DEBUG etc.: CFLAGS: LDFLAGS: ABI: Settings from the global environment: CC: /usr/bin/clang CFLAGS: (CPPFLAGS, CXX and CXXFLAGS are listed below; these don't get modified.) Using
Re: [sage-devel] load_ipython_extension()
On 2015-06-17 17:40, William Stein wrote: Also IPython is large and takes a long time to load. In the past I've often tried to keep IPython from loading by default if it isn't needed, to reduce the startup time (similar to not importing numpy by default). Needs review at http://trac.sagemath.org/ticket/18726 -- 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.
Re: [sage-devel] Automatic test of optional packages+updates
this is http://trac.sagemath.org/ticket/18724 Needs review! On Thursday, 18 June 2015 08:56:53 UTC+1, Dima Pasechnik wrote: On Monday, 15 June 2015 00:57:44 UTC+1, vdelecroix wrote: All right. I recompiled Sage without chomp. Now, beyond the binary tree issues with bliss (#18698), I have failing doctests related to gap_database (all of them are marked with #option - database_gap) in - sage/groups/perm_gps/permgroup_named.py - sage/tests/gap_packages.py - sage/groups/perm_gps/permgroup_named.py Looks to a failure similar to the one reported by Emanuel Charpentier on sage-release. The gap packages fail to be imported sage: import sage.tests.gap_packages sage: sage.tests.gap_packages.test_packages(['atlasrep']) StatusPackageGAP Output +-+--++ Failure atlasrep fail sage: sage.tests.gap_packages.test_packages(['tomlib']) StatusPackage GAP Output +-+-++ Failure tomlibfail for these you (also) need database_gap The error message in sage: gap.load_package(tomlib) --- RuntimeError Traceback (most recent call last) ipython-input-1-cc487c826f42 in module() 1 gap.load_package(tomlib) /home/dima/software/sage/local/lib/python2.7/site-packages/sage/interfaces/gap.pyc in load_package(self, pkg, verbose) 504 if x == 'fail': 505 raise RuntimeError(Error loading Gap package +str(pkg)+. + -- 506You may want to install the gap_packages SPKG.) 507 508 def eval(self, x, newlines=False, strip=True, split_lines=True, **kwds): RuntimeError: Error loading Gap package tomlib. You may want to install the gap_packages SPKG. After installing database_gap, atlasrep loads, too Let me see how to fix this. Vincent On 14/06/15 10:32, Frédéric Chapoton wrote: according to #16364, chomp could lead to this kind of things. But it is not in your list !! Le dimanche 14 juin 2015 10:29:33 UTC+2, Frédéric Chapoton a écrit : For binary trees, I have made http://trac.sagemath.org/ticket/18698 that needs review. Le dimanche 14 juin 2015 10:19:22 UTC+2, Frédéric Chapoton a écrit : Indeed, the failure for binary trees should come from canonical labeling. It would be enough to change the doctest so that they are no longer sensitive to that. I am no longer that sure that TOPCOM is the other problem. What other package is delaing with homology ? chomp ? Frederic Le dimanche 14 juin 2015 10:09:23 UTC+2, Nathann Cohen a écrit : I would suspect that topcom should be responsible for the homology errors. No idea for what happens to binary trees. They seem to be reversed (left-right symmetry ?) That could be 'bliss'. It becomes the default algorithm to compute automorphism groups of graphs and canonical representatives. Those canonical representatives will be different from the previous ones, though. Nathann -- 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.
[sage-devel] Re: problem posting on trac
I just posted a comment on this ticket, no problem... On Thursday, 18 June 2015 03:45:49 UTC+1, François wrote: Hi all, I seem to have trouble posting on trac. I successfully updated a ticket 3 hours ago and since then I have tried posting on http://trac.sagemath.org/ticket/17618 but it just times out on me after I hit the submit change button. I can see tickets just fine. Francois -- 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.
Re: [sage-devel] Automatic test of optional packages+updates
On Monday, 15 June 2015 00:57:44 UTC+1, vdelecroix wrote: All right. I recompiled Sage without chomp. Now, beyond the binary tree issues with bliss (#18698), I have failing doctests related to gap_database (all of them are marked with #option - database_gap) in - sage/groups/perm_gps/permgroup_named.py - sage/tests/gap_packages.py - sage/groups/perm_gps/permgroup_named.py Looks to a failure similar to the one reported by Emanuel Charpentier on sage-release. The gap packages fail to be imported sage: import sage.tests.gap_packages sage: sage.tests.gap_packages.test_packages(['atlasrep']) StatusPackageGAP Output +-+--++ Failure atlasrep fail sage: sage.tests.gap_packages.test_packages(['tomlib']) StatusPackage GAP Output +-+-++ Failure tomlibfail for these you (also) need database_gap The error message in sage: gap.load_package(tomlib) --- RuntimeError Traceback (most recent call last) ipython-input-1-cc487c826f42 in module() 1 gap.load_package(tomlib) /home/dima/software/sage/local/lib/python2.7/site-packages/sage/interfaces/gap.pyc in load_package(self, pkg, verbose) 504 if x == 'fail': 505 raise RuntimeError(Error loading Gap package +str(pkg)+. + -- 506You may want to install the gap_packages SPKG.) 507 508 def eval(self, x, newlines=False, strip=True, split_lines=True, **kwds): RuntimeError: Error loading Gap package tomlib. You may want to install the gap_packages SPKG. After installing database_gap, atlasrep loads, too Let me see how to fix this. Vincent On 14/06/15 10:32, Frédéric Chapoton wrote: according to #16364, chomp could lead to this kind of things. But it is not in your list !! Le dimanche 14 juin 2015 10:29:33 UTC+2, Frédéric Chapoton a écrit : For binary trees, I have made http://trac.sagemath.org/ticket/18698 that needs review. Le dimanche 14 juin 2015 10:19:22 UTC+2, Frédéric Chapoton a écrit : Indeed, the failure for binary trees should come from canonical labeling. It would be enough to change the doctest so that they are no longer sensitive to that. I am no longer that sure that TOPCOM is the other problem. What other package is delaing with homology ? chomp ? Frederic Le dimanche 14 juin 2015 10:09:23 UTC+2, Nathann Cohen a écrit : I would suspect that topcom should be responsible for the homology errors. No idea for what happens to binary trees. They seem to be reversed (left-right symmetry ?) That could be 'bliss'. It becomes the default algorithm to compute automorphism groups of graphs and canonical representatives. Those canonical representatives will be different from the previous ones, though. Nathann -- 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.
