[sage-devel] Re: Sage build from source fails on OS X 10.9
It may be useful to mention here that I did manage to build with my default .bashrc in the end, so with Homebrew installed and /usr/local/ in the PATH. The issue here, as far as I understand, is that Homebrew has an installation option --with-default-names, which, if set, places utils in /usr/local/ that have the same name as those in /usr/bin. With the PATH that is typically specified after a Homebrew installation, these newly installed tools get run during the installation of Sage, which causes failure since they are not the system default. I had opted for such an installation for the Homebrew packages findutils, gnu-indent, gnu-sed, gnu-tar, gnu-which, gnutls, grep and gawk. In the end I ran brew uninstall [package]; brew install [package] for all of these (so without the --with-default-names option), which gives them a proper g prefix. After this aliases can still be set in .bashrc, which gives a completely similar user experience, but without these conflicts, since scripts do not use these aliases. The only thing that still happened is that since Sage insists on echoing all shell variables at the beginning of the installation, all the resulting text was displayed in green because of the presence of a certain LESS_TERMCAP variable. So I have the impression that Sage is compatible with a running Homebrew installation as long as the user has never used a --with-default-names option. Best, Jeroen On Monday, August 10, 2015 at 7:43:36 AM UTC-4, Jeroen Sijsling wrote: > > I opted for kicking my .bashrc out of the way and exporting a different > PATH. Regardless, I now have a working Sage build! Thank you for solving my > problem in two sentences :-) > > On Sunday, August 9, 2015 at 6:40:58 PM UTC-4, Volker Braun wrote: >> >> Building with homebrew in /usr/local is not supported and likely to >> fail. Move /usr/local out of the way and try again. >> >> >> >> On Sunday, August 9, 2015 at 11:53:51 PM UTC+2, Jeroen Sijsling wrote: >>> >>> Dear all, >>> >>> Today I tried to build Sage from source, for now just for the heck of >>> it, but also because in the future I will probably want to contribute some >>> code. Here is what happens after cloning from GitHub and typing make: >>> >>> >>> >>> Error installing package gcc-4.9.2.p1 >>> >>> Please email sage-devel (http://groups.google.com/group/sage-devel) >>> explaining the problem and including the relevant part of the log file >>> /Users/jrsijsling/Programs/sage/logs/pkgs/gcc-4.9.2.p1.log >>> Describe your computer, operating system, etc. >>> If you want to try to fix the problem yourself, *don't* just cd to >>> /Users/jrsijsling/Programs/sage/local/var/tmp/sage/build/gcc-4.9.2.p1 >>> 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 >>> '/Users/jrsijsling/Programs/sage/local/var/tmp/sage/build/gcc-4.9.2.p1' && >>> '/Users/jrsijsling/Programs/sage/sage' --sh) >>> When you are done debugging, you can type "exit" to leave the subshell. >>> >>> make[2]: *** >>> [/Users/jrsijsling/Programs/sage/local/var/lib/sage/installed/gcc-4.9.2.p1] >>> Error 1 >>> make[1]: *** [all-toolchain] Error 2 >>> >>> real 21m12.146s >>> user 14m47.666s >>> sys 4m19.776s >>> *** >>> Error building Sage. >>> >>> The following package(s) may have failed to build (not necessarily >>> during this run of 'make all'): >>> >>> * package: gcc-4.9.2.p1 >>> log file: /Users/jrsijsling/Programs/sage/logs/pkgs/gcc-4.9.2.p1.log >>> build directory: >>> /Users/jrsijsling/Programs/sage/local/var/tmp/sage/build/gcc-4.9.2.p1 >>> >>> 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 >>> >>> >>> I have not a clue where to look in this log file so I have simply >>> appended it integrally. Some more information that could be relevant: >>> >>> My computer runs OS X 10.9 (Mavericks). While I do not have Xcode, I do >>> have the command line tools. My C compiler comes from there, and gcc -v >>> gives >>> >>> Configured with: --prefix=/Library/Developer/CommandLineTools/usr >>> --with-gxx-include-dir=/usr/include/c++/4.2.1 >>> Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn) >>> Target: x86_64-apple-darwin13.4.0 >>> Thread model: posix >>> >>> More tools have been installed through Homebrew; brew doctor tells me >>> that it is feeling just fine except that "Putting non-prefixed findutils in >>> yo
[sage-devel] Re: Sage build from source fails on OS X 10.9
I opted for kicking my .bashrc out of the way and exporting a different PATH. Regardless, I now have a working Sage build! Thank you for solving my problem in two sentences :-) On Sunday, August 9, 2015 at 6:40:58 PM UTC-4, Volker Braun wrote: > > Building with homebrew in /usr/local is not supported and likely to fail. > Move /usr/local out of the way and try again. > > > > On Sunday, August 9, 2015 at 11:53:51 PM UTC+2, Jeroen Sijsling wrote: >> >> Dear all, >> >> Today I tried to build Sage from source, for now just for the heck of it, >> but also because in the future I will probably want to contribute some >> code. Here is what happens after cloning from GitHub and typing make: >> >> >> >> Error installing package gcc-4.9.2.p1 >> >> Please email sage-devel (http://groups.google.com/group/sage-devel) >> explaining the problem and including the relevant part of the log file >> /Users/jrsijsling/Programs/sage/logs/pkgs/gcc-4.9.2.p1.log >> Describe your computer, operating system, etc. >> If you want to try to fix the problem yourself, *don't* just cd to >> /Users/jrsijsling/Programs/sage/local/var/tmp/sage/build/gcc-4.9.2.p1 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 >> '/Users/jrsijsling/Programs/sage/local/var/tmp/sage/build/gcc-4.9.2.p1' && >> '/Users/jrsijsling/Programs/sage/sage' --sh) >> When you are done debugging, you can type "exit" to leave the subshell. >> >> make[2]: *** >> [/Users/jrsijsling/Programs/sage/local/var/lib/sage/installed/gcc-4.9.2.p1] >> Error 1 >> make[1]: *** [all-toolchain] Error 2 >> >> real 21m12.146s >> user 14m47.666s >> sys 4m19.776s >> *** >> Error building Sage. >> >> The following package(s) may have failed to build (not necessarily >> during this run of 'make all'): >> >> * package: gcc-4.9.2.p1 >> log file: /Users/jrsijsling/Programs/sage/logs/pkgs/gcc-4.9.2.p1.log >> build directory: >> /Users/jrsijsling/Programs/sage/local/var/tmp/sage/build/gcc-4.9.2.p1 >> >> 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 >> >> >> I have not a clue where to look in this log file so I have simply >> appended it integrally. Some more information that could be relevant: >> >> My computer runs OS X 10.9 (Mavericks). While I do not have Xcode, I do >> have the command line tools. My C compiler comes from there, and gcc -v >> gives >> >> Configured with: --prefix=/Library/Developer/CommandLineTools/usr >> --with-gxx-include-dir=/usr/include/c++/4.2.1 >> Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn) >> Target: x86_64-apple-darwin13.4.0 >> Thread model: posix >> >> More tools have been installed through Homebrew; brew doctor tells me >> that it is feeling just fine except that "Putting non-prefixed findutils in >> your path can cause python builds to fail." >> >> My binary for 6.8 runs without a hitch, and I seem to recall that >> development could be done from there as well; but I am still quite curious >> if it is possible to build from source. Many thanks in advance for your >> help! >> >> Best regards, >> Jeroen Sijsling >> > -- 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: Sage build from source fails on OS X 10.9
Building with homebrew in /usr/local is not supported and likely to fail. Move /usr/local out of the way and try again. On Sunday, August 9, 2015 at 11:53:51 PM UTC+2, Jeroen Sijsling wrote: > > Dear all, > > Today I tried to build Sage from source, for now just for the heck of it, > but also because in the future I will probably want to contribute some > code. Here is what happens after cloning from GitHub and typing make: > > > > Error installing package gcc-4.9.2.p1 > > Please email sage-devel (http://groups.google.com/group/sage-devel) > explaining the problem and including the relevant part of the log file > /Users/jrsijsling/Programs/sage/logs/pkgs/gcc-4.9.2.p1.log > Describe your computer, operating system, etc. > If you want to try to fix the problem yourself, *don't* just cd to > /Users/jrsijsling/Programs/sage/local/var/tmp/sage/build/gcc-4.9.2.p1 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 > '/Users/jrsijsling/Programs/sage/local/var/tmp/sage/build/gcc-4.9.2.p1' && > '/Users/jrsijsling/Programs/sage/sage' --sh) > When you are done debugging, you can type "exit" to leave the subshell. > > make[2]: *** > [/Users/jrsijsling/Programs/sage/local/var/lib/sage/installed/gcc-4.9.2.p1] > Error 1 > make[1]: *** [all-toolchain] Error 2 > > real 21m12.146s > user 14m47.666s > sys 4m19.776s > *** > Error building Sage. > > The following package(s) may have failed to build (not necessarily > during this run of 'make all'): > > * package: gcc-4.9.2.p1 > log file: /Users/jrsijsling/Programs/sage/logs/pkgs/gcc-4.9.2.p1.log > build directory: > /Users/jrsijsling/Programs/sage/local/var/tmp/sage/build/gcc-4.9.2.p1 > > 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 > > > I have not a clue where to look in this log file so I have simply appended > it integrally. Some more information that could be relevant: > > My computer runs OS X 10.9 (Mavericks). While I do not have Xcode, I do > have the command line tools. My C compiler comes from there, and gcc -v > gives > > Configured with: --prefix=/Library/Developer/CommandLineTools/usr > --with-gxx-include-dir=/usr/include/c++/4.2.1 > Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn) > Target: x86_64-apple-darwin13.4.0 > Thread model: posix > > More tools have been installed through Homebrew; brew doctor tells me that > it is feeling just fine except that "Putting non-prefixed findutils in your > path can cause python builds to fail." > > My binary for 6.8 runs without a hitch, and I seem to recall that > development could be done from there as well; but I am still quite curious > if it is possible to build from source. Many thanks in advance for your > help! > > Best regards, > Jeroen Sijsling > -- 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.
