source: vis_dev/glu-2.3/README @ 83

Last change on this file since 83 was 13, checked in by cecile, 13 years ago

library glu 2.3

File size: 6.9 KB
Line 
1This is release 2.3 of GLU, a set of BDD packages and low-level utilities.
2
3If you downloaded this to compile it with VIS, stop here -- see the README
4file in the VIS distribution for build and installation instructions.
5
6---------------------------------------------------------------------------
7To build GLU, you will need
8
9        * An ANSI C compiler (gcc will do, as will several versions of cc)
10        * GNU's make utility
11        * GNU's gzip utility
12        * Approximately 20 MB of free disk for the build
13        * Approximately 10 MB of free disk space for the installation
14
15---------------------------------------------------------------------------
16* Useful Addresses
17
18For the most recent version of GLU:
19        ftp://vlsi.colorado.edu/pub/vis/
20
21The VIS home page:
22        http://vlsi.colorado.edu/~vis/
23
24For the most recent version of the GNU tools:
25        http://www.gnu.org
26
27---------------------------------------------------------------------------
28This is the list of architecture/operating system/compiler
29combinations we have tested. (For installation with compilers marked
30with (*) please refer to the Platform Specific Instructions.)
31
32        * Intel ia32 / Linux / gcc, g++
33        * Intel x86_64 / Linux / gcc, g++, icc(*)
34        * Intel ia32/x86_64 / Windows XP with Cygwin 1.5.16-1 / gcc, g++(*)
35        * Intel ia32 / Mac OS X / gcc(*)
36
37The following platforms are no longer supported, but should still work.
38
39        * IBM RISC System/6000 / AIX Version 4.3.3 / gcc(*)
40        * Intel ia64 / Linux / gcc
41        * Sun Sparc/ Solaris 2.8 / gcc, g++, cc(*)
42
43The following instructions are for the generic build process.  Before
44building the tool please refer to the section "* Platform Specific
45Instructions".
46
47---------------------------------------------------------------------------
48To build GLU for a single operating system:
49
50* Download the most recent versions of GLU from the address above
51
52* Move to where you would like the GLU source to reside and unpack
53  the distribution:
54
55        % cd /home/vis                                  # for example
56        % gzip -dc /tmp/glu-2.3.tar.gz | tar xf -
57
58* Move into the glu-2.3 directory and run configure, which will determine
59  some system-specific parameters and create the Makefile:
60
61        % cd glu-2.3
62        % ./configure
63
64  By default, this will use your system's native compiler.  To use gcc,
65 
66        % ./configure --enable-gcc
67
68  (You may wish to do this because you don't have the native compiler
69  installed or because it is not ANSI.)
70
71  Note: For some platforms where VIS is not supported for the native
72  compiler, the default compiler is set to gcc.
73
74  You can also compile glu with g++.  To do so,
75
76        % ./configure --enable-gcc=g++
77
78  Note: The Makefile by default uses the "-g" option for
79  compilation.  The resultant executables may be much larger than
80  those generated without using the "-g" option.  Using the
81  "-g" option however, provides debugging capabilities.
82
83  Note: The following is of interest only to people developing code
84  within vis.  For full debugging support, specify
85  --with-comp-mode=debug.  This will turn off optimization, and turn
86  on the assertions (sanity checks) in the code.  Similarly,
87  --with-comp-mode=purify and --with-comp-mode=quantify will link vis
88  with IBM Rational's Purify or Quantify tool.
89
90* Build the GLU system by running GNU's gmake utility:
91
92        % gmake
93
94  You may not have GNU make installed on your system under the name
95  'gmake' -- try make.  If this fails, you probably need the latest
96  version of GNU's make program -- download it from the address above.
97
98* (Optional) Test the build by invoking
99
100        % gmake check
101
102  This make take some time on slower machines.
103
104* Install the GLU library and its headers:
105
106        % gmake install                                 # optional
107
108  By default, this will put binaries, libraries, headers, and help files
109  in /usr/local/bin, /usr/local/lib, /usr/local/include, and /usr/local/share
110  respectively.  To choose a different location, provide a default prefix
111  when you invoke configure, e.g., to install in /projects/glu/bin, etc.,
112  use
113
114        % ./configure --prefix=/projects/glu
115
116  when configuring GLU.
117
118---------------------------------------------------------------------------
119To install GLU on multiple operating systems off the same source tree,
120see the file "INSTALL" in this directory.
121---------------------------------------------------------------------------
122
123* Platform Specific Instructions
124
125Note: some instructions apply to platforms we no longer support.
126
127** Little-endian machines:
128
129  vis-cal will occasionally fail when compiled with
130  --with-comp-mode=debug on little-endian machines like the Alphas and
131  the Intel ix86 CPUs.
132
133** x86_64 machines:
134
135  Compilation is possible in both 64 and 32-bit modes.
136
137  For 32-bit compilation with gcc, make sure the appropriate libraries
138  are installed.  On Ubuntu, for instance, you need the multilib-g++
139  package.  Configure with --enable-gcc="gcc -m32".
140
141  With the Intel compiler (icc), the choice between 64 and 32-bit
142  modes is made when the compiler variables are initialized.  Once
143  that is done, configure with --enable-gcc=icc.
144
145** Mac OS X:
146
147  For correct operation of the CMU BDD package, uncomment the definition
148  of USE_MALLOC_FREE at line 126 of src/mem/memint.h.
149
150** Solaris:
151
152  If Sun's C compiler is not installed on your system, use gcc
153  (./configure --enable-gcc).
154
155  Warnings about redefined symbol are harmless, so are the warnings that say
156  "end-of-loop code not reached".
157
158  The target check-cmu (which is executed as part of "make check")
159  fails with Solaris's native compiler unless -dalign is removed from
160  CFLAGS.  Although vis-cmu executes correctly even if compiled with
161  -dalign, if you plan to extensively use vis-cmu (especially develop
162  new code that uses MTBDDs) you should not compile with -dalign.
163
164  The sun cc compiler (Workshop 6 update 1) on ix86 appears to have a
165  bug in the optimization routines.  The -xO4 an -xO5 compiler options
166  will make vis crash.  As a safety precaution, we have changed the
167  optimization flag to be -xO3 for all Sun platforms that use the cc
168  compiler.  You can try higher optimization flags on your machine.
169  In general, it is hard to determine cc options that will give
170  optimal results on every platform, so it may pay off to play around
171  with the optimization options.
172
173** MS Windows with Cygwin:
174
175  You need Red Hat's Cygwin environment (freely available from
176  http://www.cygwin.com) to build GLU and VIS.
177
178  With Cygwin the configuration script automatically selects gcc.
179
180** AIX:
181
182  The configuration script automatically selects gcc.  The cal package
183  occasionally produces incorrect result if compiled with optimization
184  turned on.  If you plan to use the cal BDD package with AIX, you
185  should configure glu with --with-comp-mode=debug.
186
187** DEC Alpha:
188
189  Warnings about MIN and MAX are harmless.
190  Warnings in the cuBdd package related to floating point are
191  also harmless.
192
193  The cc compiler will use 32-bit pointers by default.  To use 64-bit
194  pointers, invoke configure as follows:
195
196        % ./configure --enable-64
197
198  The gcc compiler will always use 64-bit pointers.
199
Note: See TracBrowser for help on using the repository browser.