Unless you are prepared to compile a fairly complex software system written in C/C++ we recommend that you check for a binary installation of Open GENIE and install that instead :-).
Source code installation is normally more complicated than the Binary installation but it is useful if:
It is also very likely that you will need to have some familiarity with the C, C++ and FORTRAN compilers on your system. Generally we would recommend that you install GNU g++ and use either g77 or the native FORTRAN compiler for building Open GENIE.
Before embarking on a source code build, it may well be worth mailing us at genie@isise.rl.ac.uk to check that we are not planning to do a similar build or that someone else has not already done one.
The source code is distributed in a compressed tar file which you will need to unwind in a suitable development area. The PGPLOT and Splash libraries are distributed as separate distributions which will need to be unpacked in pgplot and splash subdirectories respectively. Following this the trees must be patched to update them with modifications and files added for Open GENIE. The commands needed will be similar to the ones shown below.
cat genie-1.1.tar.gz | gunzip | tar xf - cd genie-1.1 cat ../pgplot5.1.1.tar.gz | gunzip | tar xf - cd splash cat ../../splash1.7.tar.Z | gunzip | tar xf -
The pgplot tree should now be in the "pgplot" subdirectory and splash in the "splash" subdirectory. The patches can be applied with the commands
cd genie-1.1/pgplot patch -p2 -s < pgplot-5.1.1.patch cd ../splash patch -p2 -s < splash-1.7.patch
These patches should apply fully without asking questions, if you get a question such as "File to patch:", check that pgplot and splash were extracted correctly so that the paths "genie-1.1/pgplot/makemake" and "genie-1.1/splash/Makefile.in" both point to valid files.
Ideally, the code will now build automatically if you type.
cd genie-1.1 ./configure make all
this builds the development version of Open GENIE which can be run by typing "./parser" from within the "src" direcotory. To go the whole way and build an install kit you will need to do a
make kit
to build a compressed tar file for a binary installation. This can then be installed to a users directory or system wide as described in the section on Binary Installation. Note that to build a kit you will also need a copy of GNU autoconf installed (see ftp://ftp.nd.rl.ac.uk/pub/packages/gnu).
If you are struggling we will give advice on genie@isise.rl.ac.uk. When you do contact us for advice, please provide us with examples of the errors that occur in the mail message. Remember that we probably can only guess at what might be wrong as we are unlikely to have the same system that you have to test things on.
Please check out the operating system specific notes below, they could save you a lot of time !