MinGW (http://www.mingw.org/) are known to work.
* The GNU Scientific Library (http://www.gnu.org/software/gsl/),
- version 1.6 or later, including libgslcblas included with GSL.
+ version 1.8 or later, including libgslcblas included with GSL.
* Perl (http://www.perl.org/), version 5.005_03 or later. Perl is
required during build but not after installation.
If you don't have a version already, you can install GNU
libiconv (http://www.gnu.org/software/libiconv/).
-The following package is required to enable PSPP's graphing features.
-If you cannot arrange to install it, you must run `configure' with
---without-libplot.
+ * libintl, from GNU gettext (http://ww.gnu.org/software/gettext).
+ GNU libc includes an integrated libintl, so there is no need to
+ separately install libintl on a GNU/Linux system.
- * libplot, from GNU plotutils
- (http://www.gnu.org/software/plotutils/).
+The following packages are required to enable PSPP's graphing
+features. If you cannot arrange to install them, you must run
+`configure' with --without-cairo.
+
+ * Cairo (http://cairographics.org/), version 1.5 or later.
+
+ * Pango (http://www.pango.org/), version 1.22 or later.
The following packages are required to enable PSPPIRE, the graphical
user interface for PSPP. If you cannot install them or do not wish to
* GTK+ (http://www.gtk.org/), version 2.12.0 or later.
- * libglade (http://www.jamesh.id.au/software/libglade/), version
- 2.6 or later.
+To cross-compile PSPP, you will likely need to set the
+PKG_CONFIG_LIBDIR environment variable to point to an
+appropriate pkg-config for the cross-compilation environment.
Installing the following packages will allow your PSPP binary to read
Gnumeric files.
- * pkg-config (http://pkg-config.freedesktop.org/wiki/). Versions
- 0.18 and 0.19 have a bug that will prevent library detection,
- but other versions should be fine.
+ * zlib (http://www.zlib.net/).
- To cross-compile PSPP, you will likely need to set the
- PKG_CONFIG_LIBDIR environment variable to point to an
- appropriate pkg-config for the cross-compilation environment.
+ * libxml2 (http://xmlsoft.org/).
- * zlib (http://www.zlib.net/).
+Installing the following packages will allow your PSPP binary to write
+OpenDocument text (ODT) files:
* libxml2 (http://xmlsoft.org/).
later. Installing Texinfo will allow you to build PSPP
documentation in PostScript or PDF format.
- * libpq, from Postgresql (http://postgresql.org). This enables PSPP
- to read Postgresql databases.
+ * libpq, from Postgresql (http://postgresql.org). This enables PSPP
+ to read Postgresql databases. The tests for the Postgresql
+ interface, but not the Postgresql interface itself, requires the
+ Postgresql server to be installed.
+
+ * The Text::Diff module for Perl (http://cpan.org). This enables
+ PSPP to test the Perl module more thoroughly. It is not needed
+ to build or use the Perl module.
Basic Installation
==================
root permissions. If you cannot get root permissions, see
"Installation Names", below.
+ Please note: The `make install' target does NOT install the perl
+ module (see below). To install the perl module, you must change to
+ the `perl-module' directory and manually run `make install' there.
+
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
Optional Features
=================
-`--without-libplot'
- Don't compile in support for charts (using libplot). This is
- useful if your system doesn't have the libplot library.
+`--without-cairo'
+ Don't compile in support for charts (using Cairo and Pango). This
+ is useful if your system lacks these libraries.
`--without-gui'
Don't build the PSPPIRE gui. Use this option if you only want to
build the command line version of PSPP.
+ Cairo and Pango required to build the GUI, so --without-cairo
+ implies --without-gui.
+
`--with-gui-tools'
Build the gui developer tools. There is no reason to use this
option unless you're involved with the development of PSPP
In these cases you can use --without-lib{xx} to force configure
to disregard it.
+`--without-perl-module'
+ Disable building the Perl module, in case it does not build properly
+ or you do not need it.
+
`--enable-anachronistic-dependencies'
If you use this option, some of the checks for dependent libraries
will be relaxed, permitting configure to succeed when older versions