File: INSTALL

package info (click to toggle)
garlic 1.4-1
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 4,192 kB
  • ctags: 1,368
  • sloc: ansic: 49,603; makefile: 1,079
file content (119 lines) | stat: -rw-r--r-- 4,956 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119

			Garlic Installation

Garlic is the most portable molecular viewer/editor in the unix world,
because the only libraries required by this program are the standard
C library (libc), the standard math library (libm) and the standard
X library (libX11). All other molecular visualization programs require
some additional libraries.

Before starting the installation, you might be interested to check the
technical requirements. Most contemporary unix and unix-like systems
(like linux) meet these requirements without need to change the
configuration, so you can skip this text if you are impatient.

If you have Apple McIntosh running Xtools from Tenon, please read the hints
contributed by Chris from Macinchem:

http://garlic.mefos.hr/garlic-1.4/install/macosx.html

To compile and install garlic, follow these instructions:

 (1) Put garlic package (garlic-1.4.tar.gz) into some empty directory.

 (2) Uncompress and unpack the package:
     gzip -d garlic-1.4.tar.gz
     tar xf garlic-1.4.tar

 (3) Change your working directory:
     cd garlic-1.4

 (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, it will take 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 and the file which contains the
     template residues should be copied to a directory where these files 
     will be accessible to everyone. If this is not done, garlic will work
     anyway, using hard-coded default configuration, but you will be unable
     to replace residues and to create peptides.
     The recommended directory is /usr/local/lib/garlic but if directory
     /usr/local/lib does not exist on your system, /usr/lib/garlic may be
     may be used. This should be done by root (system administrator):
     mkdir /usr/local/lib/garlic
     cp .garlicrc /usr/local/lib/garlic
     cp residues.pdb /usr/local/lib/garlic

(10) It may be good idea to copy the configuration file to your home
     directory or to the subdirectory garlic of your home directory.
     The same may be done with the file residues.pdb. If you do this,
     you will be able to personalize your garlic sessions, because your
     private files will override the system-wide defaults. Of course,
     you don't need root privileges to do this:
     cp .garlicrc $HOME
     cp residues.pdb $HOME
     or:
     mkdir $HOME/garlic
     cp .garlicrc $HOME/garlic
     cp residues.pdb $HOME/garlic

(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. Detailed instructions may be found at:

     http://garlic.mefos.hr/garlic-1.4/install/mol_path.html

(12) Clean up the mess (sources and .o files). Be sure to leave all .pdb
     files for later practice. Leave also the files with the extension
     .script, these are some garlic tutorial scripts.

If garlic refuses to work because it fails to get the TrueColor visual,
try to execute xdpyinfo and xwininfo (click into the root window); check
the list of supported visuals and the current color depth. Choose the color
depth for which the TrueColor visual is available. If you have the SGI
Octane workstation, please read the text, contributed by Randal R. Ketchem:

http://garlic.mefos.hr/garlic-1.4/install/octane.html

If you have IBM RS6000 with AIX, read the hint, contributed by Nicolas Ferre:

http://garlic.mefos.hr/garlic-1.4/install/rs6000.html

The list of sites with proteins, nucleic acids and hetero compounds may be
found at:

http://garlic.mefos.hr/garlic-1.4/data/index.html

If you can't compile, install or run garlic, write to me (Damir Zucic),
my address is zucic@garlic.mefos.hr .