On Tuesday, February 14, 2012 5:14:13 PM UTC-8, R. Andrew Ohana wrote: > > On Tue, Feb 14, 2012 at 14:57, entropy wrote: > > Darn, flopped again. The mpir package "could not find a working > > compiler". Kind of ironic, since this whole thread has been about > > building gcc-4.6.2. :) From the log, it seems to have found the > > system's gcc (4.2.1, the same one that couldn't build 4.6 I suppose). > > But has issues with the following issue: "no, double -> ulong > > conversion". To be clear, after gcc-4.6.2 built and installed, in > > order to restart the build process, I simply typed "make" again in the > > sage root directory. Is it necessary to modify this command if one > > restarts a build process? Or is my problem that the built process > > should be using gcc-4.6.2 throughout once gcc-4.6.2 is built? > > Once gcc-4.6.2 is built, it should start using it. FYI, I didn't > actually test using clang for building only gcc-4.6.2, I tested it for > building all the gcc deps in addition to gcc-4.6.2. > > Specifically: > > $ CC=clang CXX=clang++ make > > compiled a fully working version of sage on sage1.cs, since it used > clang until gcc was built, and then it switched over to the newly > compiled gcc. > Why would it switch over to gcc? Wouldn't this use clang for any spkg which respects the CC environment variable, regardless of the presence of SAGE_ROOT/local/bin/gcc?
-- John -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
