Miriad binary releases

From CARMA
(Difference between revisions)
Jump to: navigation, search
Line 18: Line 18:
  
 
It is quite possible that shared libraries on your system are not compatible with the ones in our binary releases. If so, you should try an [[installation from source]].
 
It is quite possible that shared libraries on your system are not compatible with the ones in our binary releases. If so, you should try an [[installation from source]].
 +
 +
== CVS ==
 +
 +
Each binary release is CVS enabled, albeit via the CVS anonymous account. This means you can '''cvs update''' your source tree and obtain new code, but not randomly edit and expect the merge to be successfull. If this all means nothing to you, we will cover this at the Party.

Revision as of 14:40, 9 February 2007

Binary releases

See [1].

  • miriad_ia32: linux IA-32 (i386..i686)
  • miriad_ia64: linux IA-64 (amd64...)
  • miriad_ppc: darwin_ppc, compiled with gcc 4.3.0 and g77 3.4.6 from HPC, for MacOSX 10.4.8 (Tiger)
  • miriad_intel: darwin_intel, compiled with gcc 4.3.0 and g77 3.4.0 from HPC for MacOS 10.4.8 (Tiger)

Untar the file and edit the two miriad_start scripts to reflect the location on your system e.g.

 % tar zxf miriad_ARCH.tar.gz
 % emacs miriad_ARCH/miriad_start.csh      <--- adjust the path for $MIR
 % emacs miriad_ARCH/miriad_start.sh       <--- adjust the path for $MIR


Now source the appropriate startup file, depending on your shell, and miriad should now be usable in your shell. You can also make this permanent by adding this to your ~/.cshrc or ~/.bashrc file.

It is quite possible that shared libraries on your system are not compatible with the ones in our binary releases. If so, you should try an installation from source.

CVS

Each binary release is CVS enabled, albeit via the CVS anonymous account. This means you can cvs update your source tree and obtain new code, but not randomly edit and expect the merge to be successfull. If this all means nothing to you, we will cover this at the Party.

Personal tools