Hi,

On 5 Aug., 11:59, David Kirkby <david.kir...@onetel.net> wrote:
> I want to change the file prereq-0.3/configure.ac to make a new
> prereq-0.4/configure script, as currently the configure script does a
> few things I think are wrong.
>
> 1) If CC is set to a non-GNU compiler, the configure scripts tests the
> version of  gcc and says the GNU compiler is too old. I know currently
> we only support gcc, but ultimately we hope to support the Sun
> compiler. This configure script will l break such an attempt
> immediately.
>
> My proposale is to change configure.ac, so the configure script issues
> a warning other compilers are unsupported, but does not attempt to
> test their versions  - it just tries to use whatever compilers are
> specified with CC, CXX and SAGE_FORTRAN one has tried to use, after
> the warning has been issued.
>
> Is this a reasonable thing to do?
>
> 2)  The configure script does a very simple test for the version of
> gcc, and rejects it if its less than 3. It then issues a message
> "please upgrade to gcc 3.x or 4.x"
>
> The README says Sage builds with "GCC >= 3.x and GCC >= 4.1.x."
>
> Somewhere I read Sage will not build with gcc < 3.3.
>
> Also, the configure script will currently accept gcc 4.0.0, 4.0.1, yet
> they are known to be buggy.
>
> I suggest the configure script is updated to accept gcc's in the ranges
>
> 3.3.0 <= $version <= 3.4.6 (3.4.6 was the last of the 3.x releases)
> $version >= 4.1
>

on Mac OS X 10.4, we are forced to use gcc 4.0.1 (as comes with "XCode
2.5", the latest development environment available for OS X 10.4 from
Apple). Fortunately, the gcc version 4.0.1 (from Apple) "build 5370"
works fine.

Cheers,
Georg

--~--~---------~--~----~------------~-------~--~----~
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
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to