[BACK]Return to appa.tex CVS log [TXT][DIR] Up to [local] / OpenXM_contrib / pari-2.2 / doc

Diff for /OpenXM_contrib/pari-2.2/doc/Attic/appa.tex between version 1.1 and 1.2

version 1.1, 2001/10/02 11:16:56 version 1.2, 2002/09/11 07:26:41
Line 121  compiler and run into trouble with a recent \kbd{g++},
Line 121  compiler and run into trouble with a recent \kbd{g++},
   
 \subsec{Troubleshooting and fine tuning:} Decide whether you agree with what  \subsec{Troubleshooting and fine tuning:} Decide whether you agree with what
 \kbd{Configure} printed on your screen (in particular the architecture,  \kbd{Configure} printed on your screen (in particular the architecture,
 compiler and optimization flags). If anything should have been found and was  compiler and optimization flags). Look for messages prepended by
 not, consider that \kbd{Configure} failed and follow the instructions below.  \kbd{\#\#\#}, which probably report genuine problems. If anything should have
 Look especially for the \kbd{readline} and \kbd{X11} libraries, and the  been found and was not, consider that \kbd{Configure} failed and follow the
 \kbd{perl} and \kbd{gunzip} (or \kbd{zcat}) binaries.  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  In case the default \kbd{Configure} run fails miserably, try
   
Line 137  case, we would appreciate a bug report including the c
Line 138  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  \kbd{Configure} and the file \kbd{O$xxx$/dft.Config.in} that was produced in
 the process.  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  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  standard place, it won't find them. Nonetheless, it first searches the
 distribution toplevel for a \kbd{readline} directory. Thus, if you just want  distribution toplevel for a \kbd{readline} directory. Thus, if you just want
Line 147  feature together with a symbolic link, named \kbd{read
Line 149  feature together with a symbolic link, named \kbd{read
 toplevel directory if you have compiled the readline library somewhere else,  toplevel directory if you have compiled the readline library somewhere else,
 without installing it to one of its standard locations.  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  \misctitle{Technical note:} Configure can build GP on different architectures
 simultaneously from the same toplevel sources. Instead of the \kbd{readline}  simultaneously from the same toplevel sources. Instead of the \kbd{readline}
 link alluded above, you can create \kbd{readline-{\sl osname}-{\sl arch}},  link alluded above, you can create \kbd{readline-{\sl osname}-{\sl arch}},
Line 175  of PARI can be built.
Line 186  of PARI can be built.
 \noindent in the distribution directory. If your \kbd{make} program supports  \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$}  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  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}  \subsubsec{Testing}
   
 To test the binary, type \kbd{make bench}. This will build a static  To test the binary, type \kbd{make bench}. This will build a static
Line 185  run a series of comparative tests on those two. To tes
Line 202  run a series of comparative tests on those two. To tes
 binary, use \kbd{make dobench} which starts the bench immediately.  binary, use \kbd{make dobench} which starts the bench immediately.
   
 The static binary should be slightly faster. In any case, this should not  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  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  \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  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  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  installation procedure, but it may be a bug in the Pari system, in which
Line 242  printer. The output should bear some similarity to the
Line 259  printer. The output should bear some similarity to the
   
 \kbd{make install}  \kbd{make install}
   
 \noindent (You may have to do this with superuser privileges, depending on  \noindent You may have to do this with superuser privileges, depending on
 the target directories.) Beware that, if you chose the same installation  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  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  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  and executable files from newer versions (starting with version 1.900) are
Line 256  GP executable (probably \kbd{gp-dyn}) under the name \
Line 274  GP executable (probably \kbd{gp-dyn}) under the name \
 PARI library (probably \kbd{libpari.so}), the necessary include files, the  PARI library (probably \kbd{libpari.so}), the necessary include files, the
 manual pages, the documentation and help scripts and emacs macros.  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  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  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  use the target \kbd{make install-lib-sta}. You can install a statically
Line 296  current \kbd{misc/gprc.dft}.
Line 319  current \kbd{misc/gprc.dft}.
 \section{Getting Started}  \section{Getting Started}
   
 \subsec{Printable Documentation:} To print the user's guide, for which you'll  \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}  \kbd{make doc}
   
Line 376  following form (BibTeX format):
Line 399  following form (BibTeX format):
 @@manual{PARI2,  @@manual{PARI2,
     organization = "{The PARI~Group}",      organization = "{The PARI~Group}",
     title        = "{PARI/GP, Version @vers}",      title        = "{PARI/GP, Version @vers}",
     year         = 2000,      year         = 2002,
     address      = "Bordeaux",      address      = "Bordeaux",
     note         = "available from {\tt @wwwsite}"      note         = "available from {\tt @wwwsite}"
 }  }
Legend:
Removed from v.1.1  
changed lines
  Added in v.1.2
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>