autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [autoconf] Cray Fortran compilers


From: Paul Eggert
Subject: Re: [autoconf] Cray Fortran compilers
Date: Wed, 22 May 2002 16:41:08 -0700 (PDT)

> From: Kate Hedstrom <address@hidden>
> Date: Wed, 22 May 2002 10:05:40 -0800
> 
> Can I request that cf77 and cft77 get removed from the list of Fortran
> compilers to try? They are both old and I was surprised to find them on
> the system. Neither one passes the configure tests while f90 (for years
> the recommended compiler) does.

Thanks, I installed the following patch.  I'm CC:ing this to Wendy
Palm, who submitted Cray-related patches earlier this year, in case
there's some reason to still keep trying to use those ancient
compilers.

2002-05-22  Paul Eggert  <address@hidden>

        * lib/autoconf/fortran.m4 (AC_PROG_F77): Remove cf77 and cft77
        from the default list of compilers to try.  Suggested by
        Kate Hedstrom.
        * NEWS: Document the above.
        * autoconf.texi: Don't suggest cf77.

Index: NEWS
===================================================================
RCS file: /cvsroot/autoconf/autoconf/NEWS,v
retrieving revision 1.240
diff -p -u -r1.240 NEWS
--- NEWS        18 May 2002 00:57:30 -0000      1.240
+++ NEWS        22 May 2002 23:06:34 -0000
@@ -19,6 +19,7 @@
   that contains getloadavg.c, and it tests whether getloadavg.c exists.
 - AC_FUNC_SETVBUF_REVERSED no longer fails when cross-compiling.
 - AC_PROG_CC_STDC is integrated into AC_PROG_CC.
+- AC_PROG_F77 default search no longer includes cf77 and cfg77.
 - New macro: AC_GNU_SOURCE.
 
 ** Bug fixes
Index: doc/autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.625
diff -p -u -r1.625 autoconf.texi
--- doc/autoconf.texi   20 May 2002 09:37:27 -0000      1.625
+++ doc/autoconf.texi   22 May 2002 23:07:04 -0000
@@ -5064,7 +5064,7 @@ example, if you didn't like the default 
 @code{AC_PROG_F77} like this:
 
 @example
-AC_PROG_F77(fl32 f77 fort77 xlf cf77 g77 f90 xlf90)
+AC_PROG_F77(fl32 f77 fort77 xlf g77 f90 xlf90)
 @end example
 
 If using @code{g77} (the @sc{gnu} Fortran 77 compiler), then
Index: lib/autoconf/fortran.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/autoconf/fortran.m4,v
retrieving revision 1.158
diff -p -u -r1.158 fortran.m4
--- lib/autoconf/fortran.m4     2 Mar 2002 15:19:48 -0000       1.158
+++ lib/autoconf/fortran.m4     22 May 2002 23:07:05 -0000
@@ -232,7 +232,6 @@ AU_DEFUN([ac_cv_prog_g77],
 # `fort77' and `fc' are wrappers around `f2c', `fort77' being better.
 # It is believed that under HP-UX `fort77' is the name of the native
 # compiler.  On some Cray systems, fort77 is a native compiler.
-# cf77 and cft77 are (older) Cray F77 compilers.
 # frt is the Fujitsu F77 compiler.
 # pgf77 and pgf90 are the Portland Group F77 and F90 compilers.
 # xlf/xlf90/xlf95 are IBM (AIX) F77/F90/F95 compilers.
@@ -248,7 +247,7 @@ AC_ARG_VAR([FFLAGS], [Fortran 77 compile
 _AC_ARG_VAR_LDFLAGS()dnl
 AC_CHECK_TOOLS(F77,
       [m4_default([$1],
-                  [g77 f77 xlf cf77 cft77 frt pgf77 fl32 af77 fort77 f90 xlf90 
pgf90 epcf90 f95 fort xlf95 lf95 g95 fc])])
+                  [g77 f77 xlf frt pgf77 fl32 af77 fort77 f90 xlf90 pgf90 
epcf90 f95 fort xlf95 lf95 g95 fc])])
 
 # Provide some information about the compiler.
 echo "$as_me:__oline__:" \



reply via email to

[Prev in Thread] Current Thread [Next in Thread]