=================================================================== RCS file: /home/cvs/OpenXM_contrib/pari-2.2/doc/Attic/appa.tex,v retrieving revision 1.1 retrieving revision 1.2 diff -u -p -r1.1 -r1.2 --- OpenXM_contrib/pari-2.2/doc/Attic/appa.tex 2001/10/02 11:16:56 1.1 +++ OpenXM_contrib/pari-2.2/doc/Attic/appa.tex 2002/09/11 07:26:41 1.2 @@ -1,4 +1,4 @@ -% $Id: appa.tex,v 1.1 2001/10/02 11:16:56 noro Exp $ +% $Id: appa.tex,v 1.2 2002/09/11 07:26:41 noro Exp $ % Copyright (c) 2000 The PARI Group % % This file is part of the PARI/GP documentation @@ -121,10 +121,11 @@ compiler and run into trouble with a recent \kbd{g++}, \subsec{Troubleshooting and fine tuning:} Decide whether you agree with what \kbd{Configure} printed on your screen (in particular the architecture, -compiler and optimization flags). If anything should have been found and was -not, consider that \kbd{Configure} failed and follow the instructions below. -Look especially for the \kbd{readline} and \kbd{X11} libraries, and the -\kbd{perl} and \kbd{gunzip} (or \kbd{zcat}) binaries. +compiler and optimization flags). Look for messages prepended by +\kbd{\#\#\#}, which probably report genuine problems. If anything should have +been found and was not, consider that \kbd{Configure} failed and follow the +instructions below. Look especially for the \kbd{readline} and \kbd{X11} +libraries, and the \kbd{perl} and \kbd{gunzip} (or \kbd{zcat}) binaries. In case the default \kbd{Configure} run fails miserably, try @@ -137,7 +138,8 @@ case, we would appreciate a bug report including the c \kbd{Configure} and the file \kbd{O$xxx$/dft.Config.in} that was produced in the process. -Note that even in interactive mode, you can't directly tell \kbd{Configure} +\subsec{Problems related to readline:} +Even in interactive mode, you cannot directly tell \kbd{Configure} where the \kbd{readline} library and include files are. If they are not in a standard place, it won't find them. Nonetheless, it first searches the distribution toplevel for a \kbd{readline} directory. Thus, if you just want @@ -147,6 +149,15 @@ feature together with a symbolic link, named \kbd{read toplevel directory if you have compiled the readline library somewhere else, without installing it to one of its standard locations. +\misctitle{Linux:} Linux distributions have separate \kbd{readline} and +\kbd{readline-devel} packages. You need both of them installed to compile gp +with readline support. If only \kbd{readline} is installed, \kbd{Configure} +will complain. \kbd{Configure} may also complain about a missing +libncurses.so, in which case, you will have to install the +\kbd{ncurses-devel} package (some distributions let you install +\kbd{readline-devel} without \kbd{ncurses-devel}, which is a bug in their +package dependency handling). + \misctitle{Technical note:} Configure can build GP on different architectures simultaneously from the same toplevel sources. Instead of the \kbd{readline} link alluded above, you can create \kbd{readline-{\sl osname}-{\sl arch}}, @@ -175,8 +186,14 @@ of PARI can be built. \noindent in the distribution directory. If your \kbd{make} program supports parallel make, you can speed up the process by going to the \kbd{O$xxx$} directory that \kbd{Configure} created and doing a parallel make here (for -instance \kbd{make -j4} with GNU make). +instance \kbd{make -j4} with GNU make). It may even work from the toplevel +directory. +The GP binary built above is optimized. If you have run \kbd{Configure -g} or +\kbd{-pg} and want to build a special purpose binary, you can \kbd{cd} to the +\kbd{.dbg} or \kbd{.prf} directory and type \kbd{make gp} there. You can also +invoke \kbd{make gp.dbg} or \kbd{make gp.prf} directly from the toplevel. + \subsubsec{Testing} To test the binary, type \kbd{make bench}. This will build a static @@ -185,10 +202,10 @@ run a series of comparative tests on those two. To tes binary, use \kbd{make dobench} which starts the bench immediately. The static binary should be slightly faster. In any case, this should not -take more than one minute (user time) on modern machines. See the file -\kbd{MACHINES} to get an idea of how much time comparable systems need (we +take more than a few seconds (user time) on modern machines. See the file +\kbd{MACHINES} to get an idea of how much time comparable systems need. (We would appreciate a short note in the same format in case your system is not -listed and you nevertheless have a working GP executable). +listed and you nevertheless have a working GP executable.) If a \kbd{[BUG]} message shows up, something went wrong. Probably with the installation procedure, but it may be a bug in the Pari system, in which @@ -242,8 +259,9 @@ printer. The output should bear some similarity to the \kbd{make install} -\noindent (You may have to do this with superuser privileges, depending on -the target directories.) Beware that, if you chose the same installation +\noindent You may have to do this with superuser privileges, depending on +the target directories. (Tip for MacOS X beginners: use +\kbd{sudo make install}.) Beware that, if you chose the same installation directory as before in the \kbd{Configure} process, this will wipe out any files from version 1.39.15 and below that might already be there. Libraries and executable files from newer versions (starting with version 1.900) are @@ -256,6 +274,11 @@ GP executable (probably \kbd{gp-dyn}) under the name \ PARI library (probably \kbd{libpari.so}), the necessary include files, the manual pages, the documentation and help scripts and emacs macros. +To save on disk space, you can manually \kbd{gzip} some of the documentation +files if you wish~: \kbd{usersch*.tex} and all \kbd{dvi} files (assuming your +\kbd{xdvi} knows how to deal with compressed files); the online-help system +will handle it. + By default, if a dynamic library \kbd{libpari.so} could be built, the static library \kbd{libpari.a} will not be created. If you want it as well, you can use the target \kbd{make install-lib-sta}. You can install a statically @@ -296,7 +319,7 @@ current \kbd{misc/gprc.dft}. \section{Getting Started} \subsec{Printable Documentation:} To print the user's guide, for which you'll -need a working (plain) \TeX\ installation; type +need a working (plain) \TeX\ installation, type \kbd{make doc} @@ -376,7 +399,7 @@ following form (BibTeX format): @@manual{PARI2, organization = "{The PARI~Group}", title = "{PARI/GP, Version @vers}", - year = 2000, + year = 2002, address = "Bordeaux", note = "available from {\tt @wwwsite}" }