X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=INSTALL;h=df9502a7179485b5deb54eb9de2d9391f55b6c61;hb=65c4b7fb960b429cc535d3b564a704ee4ebfbed6;hp=dd27803865ef9c166d671977a69db93c0e6343fb;hpb=67b7ff8af7b62e8dd8d93291c12591dfea269d23;p=pspp-builds.git diff --git a/INSTALL b/INSTALL index dd278038..df9502a7 100644 --- a/INSTALL +++ b/INSTALL @@ -1,5 +1,5 @@ -PSPP Installation Instructions -****************************** +Installation Instructions for GNU pspp +************************************** These instructions are based on the generic GNU installation instructions, but they have been tailored for PSPP. @@ -33,6 +33,10 @@ The following packages are required to install PSPP: 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. @@ -48,11 +52,7 @@ use the GUI, you must run `configure' with --without-gui. 0.18 and 0.19 have a bug that will prevent library detection, but other versions should be fine. - * GTK+ (http://www.gtk.org/), version 2.8.0 or later, although we - recommend version 2.10.2 or later. - - * libglade (http://www.jamesh.id.au/software/libglade/), version - 2.6 or later. + * GTK+ (http://www.gtk.org/), version 2.12.0 or later. Installing the following packages will allow your PSPP binary to read Gnumeric files. @@ -61,6 +61,10 @@ 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/). @@ -79,6 +83,9 @@ The following packages are optional. 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. + Basic Installation ================== @@ -102,6 +109,23 @@ release. 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. @@ -120,7 +144,9 @@ release. `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 @@ -129,8 +155,9 @@ release. 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 @@ -200,6 +227,25 @@ Optional Features Build the gui developer tools. There is no reason to use this option unless you're involved with the development of PSPP +`--without-lib{xx}' + Optional libraries should normally be detected and the relevant + functionality will be built they exist. However, on some poorly + configured systems a library may exist, but be totally broken. + In these cases you can use --without-lib{xx} to force configure + to disregard 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 + 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=". Defining Variables ==================