X-Git-Url: https://www.ginac.de/ginac.git//ginac.git?p=ginac.git;a=blobdiff_plain;f=INSTALL;h=1cad2773e5a3ec6ec9aeb4008b1cd94e396b891f;hp=038ae7629cd8c69607701ab77c35df6b1c1c3800;hb=eaa0370ac188561e02195a377b252b4caf5ab57a;hpb=781107fc309db9eadc2e0540d35d9813da0afd4d diff --git a/INSTALL b/INSTALL index 038ae762..1cad2773 100644 --- a/INSTALL +++ b/INSTALL @@ -5,18 +5,34 @@ GiNaC requires the CLN library by Bruno Haible installed on your system. It is available from . You will also need a decent ANSI-compliant C++-compiler. We recommend the -C++ compiler from the GNU compiler collection, GCC >= 3.0. If you have a +C++ compiler from the GNU compiler collection, GCC >= 3.4. If you have a different or older compiler you are on your own. Note that you may have to use the same compiler you compiled CLN with because of differing name-mangling schemes. +The pkg-config utility is required for configuration, it can be downloaded +from . + +To build the GiNaC tutorial and reference manual the doxygen utility +(it can be downloaded from http://www.stack.nl/~dimitri/doxygen) and +TeX are necessary. + Known to work with: - - Linux on x86, Alpha and Sparc using GCC 3.0.x, 3.1 and 3.2. + - Linux on x86 and x86_64 using GCC 3.4, 4.0, 4.1, and 4.2. + - Linux on Alpha using GCC 3.4. + - Solaris on Sparc using GCC 3.4. + - Windows on x86 using GCC 3.4 (MinGW) Known not to work with: + - GCC 4.3.0 due to the compiler bug, + see . - GCC 2.96 or earlier because proper exception and standard library support is missing there. +If you install from CVS, you also need GNU autoconf (>=2.59), automake (>=1.7), +libtool (>= 1.5), bison (>= 2.3), flex (>= 2.5.33), autogen (>= 5.6.0) to be +installed. + INSTALLATION ============ @@ -28,17 +44,6 @@ To install from a source .tar.bz2 distribution: [become root if necessary] # make install -To install from CVS: - - $ cvs -d :pserver:anoncvs@cvsthep.physik.uni-mainz.de:/home/cvs login - [enter "anoncvs" as the password] - $ cvs -d :pserver:anoncvs@cvsthep.physik.uni-mainz.de:/home/cvs co GiNaC - $ cd GiNaC - $ ./autogen.sh - $ make - [become root if necessary] - # make install - To build the GiNaC tutorial and reference manual in HTML, DVI, PostScript, or PDF formats, use one of @@ -52,9 +57,8 @@ library works correctly you can use $ make check -The "configure" script (and "autogen.sh", which invokes "configure") can be -given a number of options to enable and disable various features. For a -complete list, type: +The "configure" script can be given a number of options to enable and +disable various features. For a complete list, type: $ ./configure --help @@ -83,6 +87,32 @@ make | ~6m | ~8m | shared and static library make check | ~8m | ~12m | largely due to compilation +To install from CVS +=================== + +First, download the code: + + $ cvs -d :pserver:anoncvs@cvs.ginac.de:/home/cvs/GiNaC login + [enter "anoncvs" as the password] + $ cvs -d :pserver:anoncvs@cvs.ginac.de:/home/cvs/GiNaC co GiNaC + $ cd GiNaC + +Secondly, make sure all required software is installed. This is *really* +important step. If some package is missing, the `configure' script might +be misgenerated, see e.g. this discussion: + + +Finally, run + + $ autoreconf -i + +to generate the `configure' script, and proceed in a standard way, i.e. + + $ ./configure + $ make + [become root if necessary] + # make install + COMMON PROBLEMS =============== @@ -96,12 +126,22 @@ install CLN properly on your system before continuing with GiNaC. Problems building ginsh ----------------------- -The most common reason why this doesn't succeed is the absence of -libreadline and/or the corresponding header files. Depending on what your -system/distribution is, you will have to install a package called -libreadline and maybe libreadline-dev. If your system's vendor doesn't -supply such packages, go to and compile -it yourself. +The GiNaC interactive shell, ginsh, makes use of GNU readline to provide +command line editing and history. If readline library and/or headers are +missing on your system, the configure script will issue a warning. In this +case you have two options: + +1) (the easiest) If you don't intend to use ginsh (i.e. if you need GiNaC +library to compile some piece of software), ignore it. ginsh builds just +fine without readline (obviously, it won't support the command line history +and editing). + +2) Install GNU readline and run the configure script once again. Depending on +what your system/distribution is, you will have to install a package called +libreadline and libreadline-dev (or readline-devel). If your system's vendor +doesn't supply such packages, go to and +compile it yourself. Note that non-GNU versions of libreadline (in particular +one shipped with Mac OS X) are not supported at the moment. Problems with missing standard header files -------------------------------------------