Testing new install
Do this in a scratch directory where there is no miriad subdirectory, in the example below we are using the always writeable (but make sure you have 300 MB free) /tmp:
cd /tmp curl ftp://ftp.astro.umd.edu/progs/bima/miriad.tar.gz | tar zxf - cd miriad cvs update ./configure --prefix=`pwd`/build F77=gfortran >& log1 (you can optionally leave off the F77= directive) make >& log2 make install >& log3
The cvs update step is optional, and may not include newly added programs if the configure script is not updated as well. The log1 step takes not even a minute, the log2 steps takes a bit longer, maybe 10 minutes, and the log3 step about 1-2 minutes. Of course it will only successfully run if you have enough things installed on your computer. See also the Requirements.
If you want to actually try and use it, do this extra step:
after this do the usual thing to load miriad in your current shell:
it will know you have the new style install, and will also recognize if there is an old-style install.
Compiling or adding a new program for MIRIAD
In your local directory (outside of $MIR) you can simply compile a miriad program as follows:
cp $MIRPROG/calib/linecal.for linecal1.for mirmake linecal1
If you want to add a new program to miriad, the corresponding Makefile.am needs to be changed. Here's a sample recipe how to add a program linecal1, a clone of linecal, to $MIRPROG/calib
cd $MIRPROG/calib cp linecal.for linecal1.for <-- the new program is a clone of linecal edit Makefile.am <-- the 5 "obvious" additions, linecal -> linecal1 edit linecal1.for cd $MIR automake --force --copy --add-missing autoconf make make install rehash
and now the new command linecal1 should be present in your shell.