Jack Howarth's detailed instructions for building gfortran

From OS X Scientific Computing

Date: Sat, 03 Dec 2005 22:38:58 -0500

From: Jack Howarth

To: William Scott

Subject: RE: gfortran

Bill,

What I have been doing for gfortran builds here is to use the attached gcc4.info with a svn checkout of the current gcc 4.1 branch. You could also modify the info to just use a snapshot release as well but I like to be able to track the cvs a little closer than that. I would note that using svn on MacOS X is pretty brutal right now due the horrible support for hardlinks in HFS. I normally pull down the latest gcc 4.1 branch with svn on a Linux box and move it over to my Mac. To pull down and package the svn just do...

svn co svn://gcc.gnu.org/svn/gcc/branches/gcc-4_1-branch gcc 
mv gcc gcc-4.1-20051204 
tar --exclude=.svn -jcvf gcc-4.1-20051204.tar.bz2 gcc-4.1-20051204 
md5sum gcc-4.1-20051204.tar.bz2

(The 20051204 should be changed to yyyymmdd or whatever you want to distinguish it.)

Note: I did this easily on Ubuntu Linux

Then just edit the gcc4.info for the current date of this revision and correct the md5sum for the tarball. As for gromacs, I am still waiting for 3.3.1 to be released before a post a new set of packages on the tracker. Since gromacs/gromacs-mpi 3.3-1 are already in fink unstable I didn't think there was a rush. The only change I could make outside of whatever fixes the 3.3.1 release will have would be to build against vecLib. If you are asking about lammpi, I am still waiting for some response on ownership of that package. The previous maintainer doesn't want it and while I said I would take it, no one has gotten back to me on that.

Jack