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 * libxml2 (http://xmlsoft.org/).
75 The following packages are required to enable PSPP's graphing
76 features. If you cannot arrange to install them, you must run
77 `configure' with --without-cairo (in which case you will get no graphing
80 * Cairo (http://cairographics.org/), version 1.12 or later.
82 * Pango (http://www.pango.org/), version 1.22 or later.
84 The following packages are required to enable PSPPIRE, the graphical
85 user interface for PSPP. If you cannot install them or do not wish to
86 use the GUI, you must run `configure' with --without-gui.
88 * pkg-config (http://pkg-config.freedesktop.org/wiki/). Versions
89 0.18 and 0.19 have a bug that will prevent library detection,
90 but other versions should be fine.
92 * GTK+ (http://www.gtk.org/), version 3.14.5 or later.
94 * GtkSourceView (http://projects.gnome.org/gtksourceview/)
95 version 3.4.0 or later.
97 * GNU Spread Sheet Widget (http://www.gnu.org/software/ssw)
99 The following packages are optional:
101 Other optional packages:
103 * libreadline and libhistory
104 (http://tiswww.case.edu/php/chet/readline/rltop.html). Without
105 them, interactive command editing and history features in the
106 text-based user interface will be disabled.
108 * Texinfo (http://www.gnu.org/software/texinfo/), version 4.7 or
109 later. Installing Texinfo will allow you to build PSPP
110 documentation in PostScript or PDF format.
112 * libpq, from Postgresql (http://postgresql.org). This enables PSPP
113 to read Postgresql databases. The tests for the Postgresql
114 interface, but not the Postgresql interface itself, requires the
115 Postgresql server to be installed.
117 * The Text::Diff module for Perl (http://cpan.org). This enables
118 PSPP to test the Perl module more thoroughly. It is not needed
119 to build or use the Perl module.
124 These are installation instructions specific to PSPP (including PSPPIRE,
125 the graphic user interface). These instructions contain the
126 information most commonly needed by people wishing to build the
127 program from source. More detailed information can be found in the
128 generic autoconf manual which is available at
129 http://www.gnu.org/software/autoconf/manual/html_node/Running-configure-Scripts.html
131 The `configure' shell script attempts to guess correct values for
132 various system-dependent variables used during compilation.
134 If you need to do unusual things to compile the package, please
135 report the problem to bug-gnu-pspp@gnu.org. We will try to figure out
136 how `configure' could work better in your situation for the next
139 The simplest way to compile PSPP is:
141 1. `cd' to the directory containing the package's source code and type
142 `./configure' to configure the package for your system.
144 You may invoke `configure' with --help to see what options are
145 available. The most common of these are listed under "Optional
148 It is best to build and install PSPP in directories whose names do
149 not contain unusual characters such as spaces or single-quotes, due
150 to limitations of the tools involved in the build process.
152 If you installed some of the libraries that PSPP uses in a
153 non-standard location (on many systems, anywhere other than
154 /usr), you may need to provide some special flags to `configure'
155 to tell it where to find them. For example, on GNU/Linux, if you
156 installed some libraries in /usr/local, then you need to invoke
157 it with at least the following options:
159 ./configure LDFLAGS='-L/usr/local/lib -Wl,-rpath,/usr/local/lib' CPPFLAGS='-I/usr/local/include'
161 Running `configure' takes awhile. While running, it prints some
162 messages telling which features it is checking for.
164 If `configure' completes successfully, it prints the message
165 "PSPP configured successfully." at the end of its run.
166 Otherwise, it may stop with a list of packages that you must
167 install before PSPP. If it does, you need to install those
168 packages, then re-run this step. Some prerequisites may be
169 omitted by passing a --without-<feature> flag to `configure' (see
170 "Optional Features", below). If you use one of these flags, then
171 the feature that it disables will not be available in your PSPP
174 `configure' may also print a list of packages that you should
175 consider installing. If you install them, then re-run
176 `configure', additional features will be available in your PSPP
179 2. Type `make' to compile the package.
181 3. Optionally, type `make check' to run the self-tests that come
182 with the package. If any of the self-tests fail, please mail
183 bug-gnu-pspp@gnu.org with the details, to give the PSPP
184 developers an opportunity to fix the problem in the next release.
186 4. Type `make install' to install the programs and any data files
187 and documentation. Ordinarily you will need root permissions to
188 do this. The "su" and "sudo" commands are common ways to obtain
189 root permissions. If you cannot get root permissions, see
190 "Installation Names", below.
192 Please note: The `make install' target does NOT install the perl
193 module (see below). To install the perl module, you must change to
194 the `perl-module' directory and manually run `make install' there.
196 5. You can remove the program binaries and object files from the
197 source code directory by typing `make clean'. To also remove the
198 files that `configure' created (so you can compile the package for
199 a different kind of computer), type `make distclean'.
201 Compilers and Options
202 =====================
204 Some systems may require unusual options for compilation or linking that the
205 `configure' script does not know about. Run `./configure --help' for
206 details on some of the pertinent environment variables.
208 You can give `configure' initial values for configuration parameters
209 by setting variables in the command line or in the environment. Here
212 ./configure CC=c89 CFLAGS=-O0 LIBS=-lposix
214 To cross-compile PSPP, you will likely need to set the
215 PKG_CONFIG_LIBDIR environment variable to point to an
216 appropriate pkg-config for the cross-compilation environment.
218 See "Defining Variables", below, for more details.
223 By default, `make install' installs PSPP's commands under
224 `/usr/local/bin', data files under `/usr/local/share', etc. You
225 can specify an installation prefix other than `/usr/local' by giving
226 `configure' the option `--prefix=PREFIX'.
228 You may wish to install PSPP on a machine where you do not have
229 root permissions. To do so, specify a prefix relative within your
230 home directory, e.g. `--prefix=$HOME' or `--prefix=$HOME/inst'. All
231 PSPP files will be installed under the prefix directory, which `make
232 install' will create if necessary. You may run PSPP directly from the
233 `bin' directory under the prefix directory as, e.g., `~/inst/bin/pspp'
234 under most shells, or for added convenience you can add the
235 installation directory to your PATH by editing a shell startup file
238 You can specify separate installation prefixes for
239 architecture-specific files and architecture-independent files. If you
240 pass the option `--exec-prefix=PREFIX' to `configure', the package uses
241 PREFIX as the prefix for installing programs and libraries.
242 Documentation and other data files still use the regular prefix.
244 In addition, if you use an unusual directory layout you can give
245 options like `--bindir=DIR' to specify different values for particular
246 kinds of files. Run `configure --help' for a list of the directories
247 you can set and what kinds of files go in them.
249 You can cause programs to be installed with an extra prefix or
250 suffix on their names by giving `configure' the option
251 `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
257 Don't compile in support for charts (using Cairo and Pango). This
258 is useful if your system lacks these libraries.
261 Don't build the PSPPIRE gui. Use this option if you only want to
262 build the command line version of PSPP.
264 Cairo and Pango required to build the GUI, so --without-cairo
265 implies --without-gui.
268 Build the gui developer tools. There is no reason to use this
269 option unless you're involved with the development of PSPP
272 Optional libraries should normally be detected and the relevant
273 functionality will be built they exist. However, on some poorly
274 configured systems a library may exist, but be totally broken.
275 In these cases you can use --without-lib{xx} to force configure
278 `--without-perl-module'
279 Disable building the Perl module, in case it does not build properly
280 or you do not need it.
282 `--enable-relocatable'
283 This option is useful for building a package which can be installed
284 into an arbitrary directory and freely copied to any other directory.
285 If you use this option, you will probably want to install the pspp
286 with a command similar to "make install DESTDIR=<destination>".
291 Variables not defined in a site shell script can be set in the
292 environment passed to `configure'. However, some packages may run
293 configure again during the build, and the customized values of these
294 variables may be lost. In order to avoid this problem, you should set
295 them in the `configure' command line, using `VAR=value'. For example:
297 ./configure CC=/usr/local2/bin/gcc
299 causes the specified `gcc' to be used as the C compiler (unless it is
300 overridden in the site shell script). Here is another example:
302 /bin/bash ./configure CONFIG_SHELL=/bin/bash
304 Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
305 configuration-related scripts to be executed by `/bin/bash'.
307 Generic `configure' Options
308 ===========================
310 `configure' also recognizes the following options to control how it operates.
314 Print a summary of the options to `configure', and exit.
318 Print the version of Autoconf used to generate the `configure'
322 Enable the cache: use and save the results of the tests in FILE,
323 traditionally `config.cache'. FILE defaults to `/dev/null' to
328 Alias for `--cache-file=config.cache'.
333 Do not print messages saying which checks are being made. To
334 suppress all normal output, redirect it to `/dev/null' (any error
335 messages will still be shown).
338 Look for the package's source code in directory DIR. Usually
339 `configure' can determine that directory automatically.
341 `configure' also accepts some other, not widely useful, options. Run
342 `configure --help' for more details.
344 ----------------------------------------------------------------------
345 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, 2007, 2013 Free
346 Software Foundation, Inc.
348 This file is free documentation; the Free Software Foundation gives
349 unlimited permission to copy, distribute and modify it.