On Tue, Apr 05, 2011 at 04:12:37PM +0100, Dr. David Kirkby wrote:
> On 04/ 5/11 03:06 PM, Bill Hart wrote:
>> One possibly data point is that GCC 4.3.2 miscompiles GMP and MPIR on
>> x86_64 and as far as I know cannot and will not be worked around.
>
> Thank you for that. I'm not going to address t
On 04/ 5/11 03:06 PM, Bill Hart wrote:
One possibly data point is that GCC 4.3.2 miscompiles GMP and MPIR on
x86_64 and as far as I know cannot and will not be worked around.
Thank you for that. I'm not going to address the issue now, but if that is the
case, we should check for gcc 4.3.2 and
For the record, the last release of the 4.3 series is gcc-4.3.5.
--
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/sa
One possibly data point is that GCC 4.3.2 miscompiles GMP and MPIR on
x86_64 and as far as I know cannot and will not be worked around.
There were also bugs in GCC 4.3.3 which miscompiled FLINT, but as far
as I know that issue never affected Sage.
On Apr 3, 8:17 am, "Dr. David Kirkby" wrote:
> T
On 3 April 2011 15:47, Dima Pasechnik wrote:
> IMHO gcc 4.3.0 is not relevant any more, and it's hard to imagine
> anyone needing to build Sage with gcc 4.3.0 now...
But it would still be nice to document whether there are issues with
gcc 4.3.0, since we claim Sage works with gcc >= 4.0.1 and tes
IMHO gcc 4.3.0 is not relevant any more, and it's hard to imagine
anyone needing to build Sage with gcc 4.3.0 now...
On Apr 3, 3:17 pm, "Dr. David Kirkby" wrote:
> The part of the sage manual dealing with installing Sage from source code
>
> http://www.sagemath.org/doc/installation/source.html
>
