| (1) | Put garlic package (garlic-1.1.tar.gz) into some empty directory. |
| (2) |
Uncompress and unpack the package:
gzip -d garlic-1.1.tar.gz tar xf garlic-1.1.tar |
| (3) |
Change your working directory:
cd garlic-1.1 |
| (4) |
Check which C compiler is available on your system.
If you don't know how to find this information, try this: man -k compiler to obtain the list of available compilers. |
| (5) |
If gcc (GNU C) compiler is not available on your system,
use your favorite editor to edit Makefile. Replace gcc in: CC = gcc line with the name of your compiler (this may be cc, for example). If gcc is available on your system, do not change the CC line. |
| (6) |
Find a directory which contains the Xlib library. Try this:
cd / find . -name libX11\* Check where is the file libX11.so (sharable library - prefered) or libX11.a (static library - reserve option). If your directory is different from /usr/X11R6/lib, modify the line: LIBPATH = -L/usr/X11R6/lib in Makefile. For example, if libX11.so is stored in /usr/shlib directory on your system, the LIBPATH should be changed to: LIBPATH = -L/usr/shlib |
| (7) |
Compile the package - just type:
make and wait some time. |
| (8) |
If everything worked fine, copy the executable to a choosen directory.
/usr/local/bin may be a good choice. This job should be done by root (system administrator): cp garlic /usr/local/bin If you don't have root privileges, ask your local administrator to install garlic, or just leave it in one of your directories. |
| (9) |
Now the .garlicrc configuration file should be copied to a directory
where it will be accessible to everyone as the public configuration script. If this is not done, garlic will work anyway, using hard-coded defaults. The recommended directory is /usr/local/lib/garlic but if /usr/local/lib does not exist on your system, /usr/lib/garlic may be used. This should be done by root (system administrator): mkdir /usr/local/lib/garlic cp .garlicrc /usr/local/lib/garlic |
| (10) |
It may be good idea to copy the configuration file to your home directory.
If you do this, you can personalize your garlic sessions, because your private configuration file overrides the system-wide defaults. Of course, you don't need root privileges for this: cp .garlicrc $HOME |
| (11) |
It is recommended to set the environment variable MOL_PATH, so garlic
will search all directories listed in this variable to find the specified file. Click here for detailed instructions. |
| (12) |
Clean up the mess (sources and .o files). Be sure to leave
trp.pdb for later practice (this is the only PDB file included in the original garlic package). Do not delete files with extension .script (tutorial scripts). |