If you don't have a version already, you can install GNU
libiconv (http://www.gnu.org/software/libiconv/).
+ * GNU make (http://www.gnu.org/software/make). Version 3.81 is
+ known to work; other versions will likely work too. Non-GNU
+ "make" programs will probably not work.
+
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.
* GTK+ (http://www.gtk.org/), version 2.12.0 or later.
- * libglade (http://www.jamesh.id.au/software/libglade/), version
- 2.6 or later.
-
Installing the following packages will allow your PSPP binary to read
Gnumeric files.
0.18 and 0.19 have a bug that will prevent library detection,
but other versions should be fine.
+ 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.
+
* zlib (http://www.zlib.net/).
* libxml2 (http://xmlsoft.org/).
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system.
+ You may invoke `configure' with --help to see what options are
+ available. The most common of these are listed under "Optional
+ Features", below.
+
+ It is best to build and install PSPP in directories whose names do
+ not contain unusual characters such as spaces or single-quotes, due
+ to limitations of the tools involved in the build process.
+
+ If you installed some of the libraries that PSPP uses in a
+ non-standard location (on many systems, anywhere other than
+ /usr), you may need to provide some special flags to `configure'
+ to tell it where to find them. For example, on GNU/Linux, if you
+ installed some libraries in /usr/local, then you need to invoke
+ it with at least the following options:
+
+ ./configure LDFLAGS='-L/usr/local/lib -Wl,-rpath,/usr/local/lib' CPPFLAGS='-I/usr/local/include'
+
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
`configure', additional features will be available in your PSPP
installation.
- 2. Type `make' to compile the package.
+ 2. Type `make' to compile the package. (If GNU make is installed
+ under a different program name, e.g. "gmake", run that program
+ instead in this step and in the following steps as well.)
3. Optionally, type `make check' to run the self-tests that come
with the package. If any of the self-tests fail, please mail
4. Type `make install' to install the programs and any data files
and documentation. Ordinarily you will need root permissions to
- do this; if you cannot get root permissions, see "Installation
- Names", below.
+ do this. The "su" and "sudo" commands are common ways to obtain
+ root permissions. If you cannot get root permissions, see
+ "Installation Names", below.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
of libraries are detected. Use of this option is not recommended.
If you use it, some features may be missing and the build may fail
with obscure error messages.
-
+
+`--enable-relocatable'
+ This option is useful for building a package which can be installed
+ into an arbitrary directory and freely copied to any other directory.
+ If you use this option, you will probably want to install the pspp
+ with a command similar to "make install DESTDIR=<distination>".
Defining Variables
==================
projects / pspp-builds.git / blobdiff