X-Git-Url: https://www.ginac.de/ginac.git//ginac.git?a=blobdiff_plain;ds=sidebyside;f=INSTALL;h=ed1c8c50f4f7a767ba00fcc345d74f6f17c9fc5b;hb=69ec860812569dbbfb9216907abbd22ff36ce54f;hp=3730e91c0489aaf8c329e6bbb316ecc0fbf2cc0e;hpb=27eccd2a3a0bf1d4f94b05950cafa4e278f173e1;p=ginac.git
diff --git a/INSTALL b/INSTALL
index 3730e91c..ed1c8c50 100644
--- a/INSTALL
+++ b/INSTALL
@@ -12,13 +12,6 @@ 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 free C++
-interpreter Cint. 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
============
@@ -29,10 +22,10 @@ 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.x and GCC 2-95.x
+ - Linux on x86, Alpha and Sparc using GCC 2-95.x.
Known not to work with:
- GCC 2.7.x or earlier because proper exception support is missing there.
@@ -56,13 +49,13 @@ 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 | ~3m | ~3m | ~7m | mostly due to compilation
+make | ~4m | ~5m | ~6m | building shared and static lib
+make check | ~20m | ~11m | ~12m | largely due to compilation
COMMON PROBLEMS
@@ -71,12 +64,11 @@ 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.
+GiNaC. When using GCC3 as compiler please use at least CLN-1.1.1
+since some parts of GiNaC won't build with CLN-1.1.
Problems with building ginsh
----------------------------
@@ -88,28 +80,3 @@ 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
-=====================================
-
-Please see to learn about Cint
-and install it prior to installing ginaccint. For the interpreter-
-compiler `makecint' to work properly, the Makefiles need to know where
-Cint has its system directory. This is usually done by exporting
-$CINTSYSDIR to point to the proper place. With GiNaC you may either
-try to export that variable and type
- $ ./configure --with-cint
-or specify it directly on the command line by saying
- $ ./configure --with-cint=/my/path/to/cintsysdir
-This variable does not have to be exported for running the installed
-binary: since the actual program is started by a launcher that sets it.
-Enjoy!
-
-Here is an overview to gives you an idea if you can expect GiNaC-cint
-to compile, install and work properly:
-
- Cint version | how it works
---------------+----------------------------------------------------------
- < 5.14.39 | `VERBOTEN' by license (please bite your favorite lawyer)
- < 5.14.39,40 | compiles but does not feel happy at all (inconsistent!)
- 5.14.41 | tested on egcs 1.1.1, gcc 2.95.2: only minor weirdnesses