gfortran on MacOS X

gfortran Building Procedure (gcc-4.3 based)

gcc-4.0 that comes with Apple's standard DevTools does not include "gfortran", the GNU fortran 95 compiler. Although its source tree does include one, building gfortran from Apple's source tree requires some patching to satisfy undefined references caused by Apple's modifications that broke Language independence. Moreover, the gfortran source files are not up-to-date and require a lot of patching to be usable: I had been using the patched versions for sometime but recently switched to gcc-4.3. In order to make gcc-4.3 coexist with Apple's gcc-4.0, I decided to configure gcc-4.3 to be installed under /usr/osxws together with other "MacOSX WS" packages. To build gcc-4.3, first get the source files from the official GCC site, cd into the source directory and do the following:

$ ./configure --prefix=/usr/osxws --disable-checking --enable-languages=c,c++,f95 --with-gmp-lib=/usr/osxws/lib --with-gmp-include=/usr/osxws/include --with-mpfr-lib=/usr/osxws/lib --with-mpfr-include=/usr/osxws/include
$ make
$ mkdir tmp
$ export CPPFLAGS='-I/usr/osxws/include'
$ make install DESTDIR=`pwd`/tmp
$ cd tmp
$ su
# chown -R root:wheel usr
# tar -zcvf gcc-4.3.0-bin.tar.gz usr
# exit

This gives you a tarball of gcc-4.3 compiler suite including gcc, g++, and gfortran, which can be expanded at the root directory to install under /usr/osxws.

How to Install a Precompiled Binary Package

A binary package is available as an RPM which can be installed using APT/RPM as

$ su
# apt-get update
# apt-get install gcc
# apt-get clean
# exit

Since the package is installed under /usr/osxws, you can use the gcc-4.3 as your default compiler suite by putting /usr/osxws/bin in front of /usr/bin in your PATH environmental variable.
 

REMARKS

• As a general rule, you should make sure that optimization does not change your results.
• Avoid too many else if's in the same level. You sometimes need to nest them, if the compiler abends.
• gfortran forbids jumping into a different "IF" block.
• gfortran does not initialize a "BLOCK DATA" even if you declare it "EXTERNAL". In order to force it, say "blkdat", initialized, I needed a trick like
  
      external blkdat
      call dummysub(blkdat)
  
  with
      subroutine dummysub(a)
      return
      end
  
  
• gfortran now returns IOSTAT=5002 (instead of IOSTAT=3 as with gcc-4.2 or older), when the EOF is reached for an random access file, which behavior is different from that of g77.
• gcc, g++, and gfortran now use system's math library (libm.dylib), whenever possible, which sometimes causes a problem, since some functions in libm behave differently from those used to be supplied by gcc-associated libraries (a typical example is "csqrt": see cernlib page).
• Here is a sample FCFLAGS I usually use to compile my legacy fortran programs:
  
      FCFLAGS = -fno-automatic -fno-second-underscore -fno-range-check