1 Installation Instructions for GNU pspp
2 **************************************
4 These instructions are based on the generic GNU installation
5 instructions, but they have been tailored for PSPP. These instructions
6 apply only to people wishing to build and install PSPP from source.
11 PSPP uses the standard GNU configuration system. Therefore, if all is well,
12 the following simple procedure should work, even on non-GNU systems:
14 tar -xzf pspp-*.tar.gz
20 Obviously, you should replace 'pspp-*' in the above, with the name of
21 the tarball you are installing.
23 In 99% of cases, that is all you have to do - FINISHED!
28 If any part of the above process fails, then it is
29 likely that one or more of the necessary prerequisites is missing
30 from your system. The following paragraphs contain highly detailed
31 information which will help you fix this.
37 Before you install PSPP, you will need to install certain prerequisite
38 packages. You may also want to install other packages that enable
39 additional functionality in PSPP. Please note, if you are installing
40 any of the libararies mentioned below using pre-prepared binary
41 packages provided by popular GNU/Linux vendors, you may need to ensure
42 that you install the "development" versions (normally postfixed with
45 If you do not know whether you have these installed already, you may
46 proceed to "Basic Installation", below. The PSPP configuration
47 process will notify you about required and optional packages that are
48 not present on your system.
50 The following packages are required to install PSPP:
52 * A C compiler and tool chain. On Unix-like systems, we
53 recommend GCC, but any modern compilation environment should
54 work. On Microsoft Windows, Cygwin (http://www.cygwin.com/) and
55 MinGW (http://www.mingw.org/) are known to work.
57 * The GNU Scientific Library (http://www.gnu.org/software/gsl/),
58 version 1.13 or later, including libgslcblas included with GSL.
60 * Perl (http://www.perl.org/), version 5.005_03 or later. Perl is
61 required during build but not after installation.
63 * iconv, which should be installed as part of a Unix-like system.
64 If you don't have a version already, you can install GNU
65 libiconv (http://www.gnu.org/software/libiconv/).
67 * libintl, from GNU gettext (http://www.gnu.org/software/gettext).
68 GNU libc includes an integrated libintl, so there is no need to
69 separately install libintl on a GNU/Linux system.
71 * zlib (http://www.zlib.net/).
73 The following packages are required to enable PSPP's graphing
74 features. If you cannot arrange to install them, you must run
75 `configure' with --without-cairo (in which case you will get no graphing
78 * Cairo (http://cairographics.org/), version 1.5 or later.
80 * Pango (http://www.pango.org/), version 1.22 or later.
82 The following packages are required to enable PSPPIRE, the graphical
83 user interface for PSPP. If you cannot install them or do not wish to
84 use the GUI, you must run `configure' with --without-gui.
86 * pkg-config (http://pkg-config.freedesktop.org/wiki/). Versions
87 0.18 and 0.19 have a bug that will prevent library detection,
88 but other versions should be fine.
90 * GTK+ (http://www.gtk.org/), version 2.24.0 - The Gtk+-3.x series will NOT work!
92 * Glib (http://www.gtk.org), version 2.32 or later
94 * GtkSourceView (http://projects.gnome.org/gtksourceview/)
97 The following packages are optional:
99 Installing the following packages will allow your PSPP program to read
102 * libxml2 (http://xmlsoft.org/).
104 Installing the following packages will allow your PSPP program to write
105 OpenDocument text (ODT) files:
107 * libxml2 (http://xmlsoft.org/).
109 Other optional packages:
111 * libncurses (http://www.gnu.org/software/ncurses/). Without it,
112 PSPP will assume it is running in an 80x25 terminal.
114 * libreadline and libhistory
115 (http://tiswww.case.edu/php/chet/readline/rltop.html). Without
116 them, interactive command editing and history features in the
117 text-based user interface will be disabled.
119 * Texinfo (http://www.gnu.org/software/texinfo/), version 4.7 or
120 later. Installing Texinfo will allow you to build PSPP
121 documentation in PostScript or PDF format.
123 * libpq, from Postgresql (http://postgresql.org). This enables PSPP
124 to read Postgresql databases. The tests for the Postgresql
125 interface, but not the Postgresql interface itself, requires the
126 Postgresql server to be installed.
128 * The Text::Diff module for Perl (http://cpan.org). This enables
129 PSPP to test the Perl module more thoroughly. It is not needed
130 to build or use the Perl module.
135 These are installation instructions specific to PSPP (including PSPPIRE,
136 the graphic user interface). These instructions contain the
137 information most commonly needed by people wishing to build the
138 program from source. More detailed information can be found in the
139 generic autoconf manual which is available at
140 http://www.gnu.org/software/autoconf/manual/html_node/Running-configure-Scripts.html
142 The `configure' shell script attempts to guess correct values for
143 various system-dependent variables used during compilation.
145 If you need to do unusual things to compile the package, please
146 report the problem to bug-gnu-pspp@gnu.org. We will try to figure out
147 how `configure' could work better in your situation for the next
150 The simplest way to compile PSPP is:
152 1. `cd' to the directory containing the package's source code and type
153 `./configure' to configure the package for your system.
155 You may invoke `configure' with --help to see what options are
156 available. The most common of these are listed under "Optional
159 It is best to build and install PSPP in directories whose names do
160 not contain unusual characters such as spaces or single-quotes, due
161 to limitations of the tools involved in the build process.
163 If you installed some of the libraries that PSPP uses in a
164 non-standard location (on many systems, anywhere other than
165 /usr), you may need to provide some special flags to `configure'
166 to tell it where to find them. For example, on GNU/Linux, if you
167 installed some libraries in /usr/local, then you need to invoke
168 it with at least the following options:
170 ./configure LDFLAGS='-L/usr/local/lib -Wl,-rpath,/usr/local/lib' CPPFLAGS='-I/usr/local/include'
172 Running `configure' takes awhile. While running, it prints some
173 messages telling which features it is checking for.
175 If `configure' completes successfully, it prints the message
176 "PSPP configured successfully." at the end of its run.
177 Otherwise, it may stop with a list of packages that you must
178 install before PSPP. If it does, you need to install those
179 packages, then re-run this step. Some prerequisites may be
180 omitted by passing a --without-<feature> flag to `configure' (see
181 "Optional Features", below). If you use one of these flags, then
182 the feature that it disables will not be available in your PSPP
185 `configure' may also print a list of packages that you should
186 consider installing. If you install them, then re-run
187 `configure', additional features will be available in your PSPP
190 2. Type `make' to compile the package.
192 3. Optionally, type `make check' to run the self-tests that come
193 with the package. If any of the self-tests fail, please mail
194 bug-gnu-pspp@gnu.org with the details, to give the PSPP
195 developers an opportunity to fix the problem in the next release.
197 4. Type `make install' to install the programs and any data files
198 and documentation. Ordinarily you will need root permissions to
199 do this. The "su" and "sudo" commands are common ways to obtain
200 root permissions. If you cannot get root permissions, see
201 "Installation Names", below.
203 Please note: The `make install' target does NOT install the perl
204 module (see below). To install the perl module, you must change to
205 the `perl-module' directory and manually run `make install' there.
207 5. You can remove the program binaries and object files from the
208 source code directory by typing `make clean'. To also remove the
209 files that `configure' created (so you can compile the package for
210 a different kind of computer), type `make distclean'.
212 Compilers and Options
213 =====================
215 Some systems may require unusual options for compilation or linking that the
216 `configure' script does not know about. Run `./configure --help' for
217 details on some of the pertinent environment variables.
219 You can give `configure' initial values for configuration parameters
220 by setting variables in the command line or in the environment. Here
223 ./configure CC=c89 CFLAGS=-O0 LIBS=-lposix
225 To cross-compile PSPP, you will likely need to set the
226 PKG_CONFIG_LIBDIR environment variable to point to an
227 appropriate pkg-config for the cross-compilation environment.
229 See "Defining Variables", below, for more details.
234 By default, `make install' installs PSPP's commands under
235 `/usr/local/bin', data files under `/usr/local/share', etc. You
236 can specify an installation prefix other than `/usr/local' by giving
237 `configure' the option `--prefix=PREFIX'.
239 You may wish to install PSPP on a machine where you do not have
240 root permissions. To do so, specify a prefix relative within your
241 home directory, e.g. `--prefix=$HOME' or `--prefix=$HOME/inst'. All
242 PSPP files will be installed under the prefix directory, which `make
243 install' will create if necessary. You may run PSPP directly from the
244 `bin' directory under the prefix directory as, e.g., `~/inst/bin/pspp'
245 under most shells, or for added convenience you can add the
246 installation directory to your PATH by editing a shell startup file
249 You can specify separate installation prefixes for
250 architecture-specific files and architecture-independent files. If you
251 pass the option `--exec-prefix=PREFIX' to `configure', the package uses
252 PREFIX as the prefix for installing programs and libraries.
253 Documentation and other data files still use the regular prefix.
255 In addition, if you use an unusual directory layout you can give
256 options like `--bindir=DIR' to specify different values for particular
257 kinds of files. Run `configure --help' for a list of the directories
258 you can set and what kinds of files go in them.
260 You can cause programs to be installed with an extra prefix or
261 suffix on their names by giving `configure' the option
262 `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
268 Don't compile in support for charts (using Cairo and Pango). This
269 is useful if your system lacks these libraries.
272 Don't build the PSPPIRE gui. Use this option if you only want to
273 build the command line version of PSPP.
275 Cairo and Pango required to build the GUI, so --without-cairo
276 implies --without-gui.
279 Build the gui developer tools. There is no reason to use this
280 option unless you're involved with the development of PSPP
283 Optional libraries should normally be detected and the relevant
284 functionality will be built they exist. However, on some poorly
285 configured systems a library may exist, but be totally broken.
286 In these cases you can use --without-lib{xx} to force configure
289 `--without-perl-module'
290 Disable building the Perl module, in case it does not build properly
291 or you do not need it.
293 `--enable-relocatable'
294 This option is useful for building a package which can be installed
295 into an arbitrary directory and freely copied to any other directory.
296 If you use this option, you will probably want to install the pspp
297 with a command similar to "make install DESTDIR=<destination>".
302 Variables not defined in a site shell script can be set in the
303 environment passed to `configure'. However, some packages may run
304 configure again during the build, and the customized values of these
305 variables may be lost. In order to avoid this problem, you should set
306 them in the `configure' command line, using `VAR=value'. For example:
308 ./configure CC=/usr/local2/bin/gcc
310 causes the specified `gcc' to be used as the C compiler (unless it is
311 overridden in the site shell script). Here is another example:
313 /bin/bash ./configure CONFIG_SHELL=/bin/bash
315 Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
316 configuration-related scripts to be executed by `/bin/bash'.
318 Generic `configure' Options
319 ===========================
321 `configure' also recognizes the following options to control how it operates.
325 Print a summary of the options to `configure', and exit.
329 Print the version of Autoconf used to generate the `configure'
333 Enable the cache: use and save the results of the tests in FILE,
334 traditionally `config.cache'. FILE defaults to `/dev/null' to
339 Alias for `--cache-file=config.cache'.
344 Do not print messages saying which checks are being made. To
345 suppress all normal output, redirect it to `/dev/null' (any error
346 messages will still be shown).
349 Look for the package's source code in directory DIR. Usually
350 `configure' can determine that directory automatically.
352 `configure' also accepts some other, not widely useful, options. Run
353 `configure --help' for more details.
355 ----------------------------------------------------------------------
356 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, 2007, 2013 Free
357 Software Foundation, Inc.
359 This file is free documentation; the Free Software Foundation gives
360 unlimited permission to copy, distribute and modify it.