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

Re: gfortran.

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: gfortran.
  • Date: Fri, 10 Aug 2007 15:02:43 -0600
Stonie,

I have added gfortran configuration in the source code tarfile for
5.10.3.
I've tested it out here during the GEMPAK workshop and found most of
the 
hidden gotchas- which are generally problems with TAB characters
embedded within continuation  lines of FORMAT and write statements, line
lengths past 72
characters and implied comments in some external code after position 72,
debug lines, and some straight out bugs with the gfortran 4.0.2 and
earlier
compiler. I have tested with gfortran 4.1.1 and 4.1.2 with FC5, 6 and 7
under
32 and 64 bits.

I haven't build all the binaries yet, but if you want to try to build
the source, its
on the www site now. The configuration is set to USE_GFORTRAN in
Gemenviron
but can be set to g77 by editing that file if desired.

Steve


On Tue, 2007-01-09 at 14:10 -0600, Stonie Cooper wrote:
> Steve,
> 
> I'm just coming up for air long enough to play with the g77  
> replacement; before I dig in, I wanted to make sure I wasn't wasting  
> my time and that you already had a config for the new gfortran compiler.
> 
> Stonie
-- 
Steve Chiswell <address@hidden>
Unidata