On Thursday, March 7, 2013 4:38:37 AM UTC-5, Jeroen Demeyer wrote: > > The Cygwin folks have an issue that GCC-4.6.3 doesn't compile ECL > properly due to a GCC bug > (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52061). > > Since this problem doesn't seem to occur with GCC-4.7.2, I would propose > to upgrade Sage's GCC to version 4.7.2. There already exists an optional >
I assume this would mostly be to avoid the need to install not just gcc, but g++ and gfortran on Cygwin? Otherwise it hardly seems worth the effort. Given that we aren't intending for most Cygwin folks to have to actually build from source, maybe this isn't necessary. Alternately, the default Cygwin install seems to come with gcc3, and perhaps that could be used to build the Sage gcc package... I guess it would be interesting to hear more about this. How does the gcc-4.7 spkg do on various Mac systems? > package for this, so basically we just need to make that optional > package standard. Several of the buildbots are already using GCC-4.7.x > or even GCC-4.8-trunk, so GCC-4.7.x should be well-tested by now and I > don't expect problems. If nobody complains, I will do this upgrade to > GCC-4.7.2. > > Note that upgrading to versions >=4.8.0 of GCC might be harder since > those versions are implemented in C++. > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
