On 05/ 4/11 08:50 AM, Jeroen Demeyer wrote:
On 2011-05-03 21:44, Volker Braun wrote:
I agree that sage-4.7 should compile with gcc-4.6.[01]. But why not
specifically excluding these two instead of an wildcard?
What if gcc 4.6.2 exhibits the same bug? I think the *safer* option is
to assume the status-quo that the bug will not be fixed. If it does get
fixed, we can still change the spkg. I am cc'ed on the relevant gcc
tickets, so I will know when the bugs get fixed.
Jeroen.
I agree with Jeroen.
I'd much rather see the fix included until such time as we know the bug has been
removed from gcc, rather than hope some distant version fixes the bug.
I've known gcc bugs to go on a for a long time - especaily those only affecting
rarer platforms.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
--
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
