Jean-Pierre Flori wrote:
On Monday, April 1, 2013 12:32:00 PM UTC+2, Jeroen Demeyer wrote:Buildbot reports no problems at all with the new GCC spkg using *default* CFLAGS, so I really think it is ready: http://trac.sagemath.org/sage_trac/ticket/14378 <http://trac.sagemath.org/sage_trac/ticket/14378> I agree, but it would be nice to report the corenrcase problems we encounter upstream, although I don't think Ill be able to track this down.
I don't think it is unusual to have GCC configured to generate (more) native code by default; in that case the CFLAGS Sage is built with don't really matter.
To me, "supported platform" doesn't mean "there exists a machine I can build Sage on [if I build and use Sage's GCC spkg]".
At the very least, we should record / document issues with other constellations. It's IMHO ok to rely on Sage's GCC if we encounter a GCC version which is more or less broadly known to be broken [on platform xy], but we shouldn't make building Sage's GCC a general prerequisite, nor should we limit testing to just the latter case, otherwise problems -- whether upstream or within Sage -- will never get fixed.
-leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- 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.
