X-Git-Url: https://www.ginac.de/ginac.git//ginac.git?p=ginac.git;a=blobdiff_plain;f=INSTALL;h=f5d6635dd4e29db599b2b49530736f33879f4c67;hp=4555857e83d9bc7f4afb3f18a8febb96bd3da2d5;hb=ff48a4c31a23d98cc818e973e71010b7d5a97af6;hpb=956eeb82c513a723e864edefa857133282cf692b
diff --git a/INSTALL b/INSTALL
index 4555857e..f5d6635d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,27 +1,17 @@
-Prerequisites
+PREREQUISITES
=============
-GiNaC requires the CLN library by Bruno Haible, available at either
-one of the following FTP-sites:
- * ,
- * or
- * .
-You will also need a decent ANSI-compliant C++-compiler. We use
-`post-EGCS' GCC, i.e GCC >= 2.95 for development so if you have a
-different 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.
-
-Optionally, GiNaC may work together with Masaharu Goto's C++
-interpreter cint (which requires that you register for commercial
-use). You may obtain it from
- * .
-Install it by following the instructions included in Cint's
-distribution before trying to compile GiNaC-cint. (See section
-`Working with the Cint C++ interpreter' below.)
-
-
-Installation
+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 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.
+
+
+INSTALLATION
============
As with any autoconfiguring GNU software, installation is as easy as this:
@@ -30,10 +20,13 @@ As with any autoconfiguring GNU software, installation is as easy as this:
$ make
$ make check
[become root if necessary]
- $ make install
+ # make install
Known to work with:
- - Linux/x86, EGCS-1.1.2 or GCC 2-95.1/2-95.2
+ - Linux on x86, Alpha and Sparc using GCC 3.0.x, 3.1 and 3.2.
+Known not to work with:
+ - GCC 2.96 or earlier because proper exception and standard library support
+ is missing there.
The "configure" script can be given a number of options to enable and
disable various features. For a complete list, type:
@@ -55,29 +48,40 @@ The time the "make" step takes depends heavily on optimization levels.
Large amounts of memory (>128MB) will be required by the compiler,
also depending on optimization. To give you a rough idea of what you
have to expect the following table may be helpful. It was measured on
-a P-III/500MHz with "enough" memory:
+an Athlon/800MHz with "enough" memory:
-step: | GCC optimization level: | comment:
- | -O0 | -O1 | -O2 |
---------------+--------+--------+--------+-------------------------------
-make | ~4m | ~6m | ~10m | building shared and static lib
-make check | ~2m | ~2m | ~7m | mostly due to compilation
+step | GCC optimization | comment
+ | -O1 | -O2 |
+--------------+---------+---------+----------------------------------------
+make | ~6m | ~8m | shared and static library
+make check | ~8m | ~12m | largely due to compilation
+COMMON PROBLEMS
+===============
+
Problems with CLN
-=================
+-----------------
-You should use at least CLN V1.0.3, since during the development of
+You should use at least CLN-1.1, since during the development of
GiNaC various bugs have been discovered and fixed in earlier versions.
-To protect you, the "configure" script checks for a feature that was
-added in V1.0.3 so it won't continue with earlier versions anyhow.
Please install CLN properly on your system before continuing with
GiNaC.
+Problems with 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.
-Working with the Cint C++ interpreter
-=====================================
+Problems with missing standard header files
+-------------------------------------------
-You need to specify
- --with-cint=$CINTSYSDIR
-...
+Building GiNaC requires many standard header files. If you get a
+configure error complaining about such missing files your compiler and
+library are probably not up to date enough and it's no worth
+continuing.