X-Git-Url: https://www.ginac.de/ginac.git//ginac.git?p=ginac.git;a=blobdiff_plain;f=INSTALL;h=5f595f562269319532669b43511e6d5730eaa364;hp=be6b5784990aa9d87f943b3c3827fa28eca54901;hb=9026864b754a92fa74102c310e8c62c3d2c3ef75;hpb=6824c9106ca8a4ce7efcd4c712f5e0d2a02adc16
diff --git a/INSTALL b/INSTALL
index be6b5784..5f595f56 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,7 +1,7 @@
PREREQUISITES
=============
-GiNaC requires the CLN library by Bruno Haible, available at either
+GiNaC requires the CLN library by Bruno Haible, available from either
one of the following FTP-sites:
* ,
* or
@@ -12,9 +12,8 @@ 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
+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
@@ -34,6 +33,8 @@ As with any autoconfiguring GNU software, installation is as easy as this:
Known to work with:
- Linux/x86, EGCS-1.1.x and GCC 2-95.x
+Known not to work with:
+ - GCC 2.7.x or earlier because proper exception 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:
@@ -85,31 +86,29 @@ 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. After that it should work fine.
-
-If you want to build a completely static ginsh and your compiler still
-complains about unresolved objects try linking with libncurses, too.
+and compile it yourself.
Working with the Cint C++ interpreter
=====================================
-The interface to the Cint C++ interpreter is currently in an alpha
-state. Please see to learn about
-Cint and install it before installing ginaccint. For the tool
-makecint to work properly it must 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
+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 on the command line saying
+or specify it directly on the command line by saying
$ ./configure --with-cint=/my/path/to/cintsysdir
-Good luck!
+Enjoy!
- Known to work with: | Known not to work with:
------------------------+----------------------------
- Cint 5.14.38 | Cint before 5.14.37
+Here is an overview to gives you an idea if you can expect GiNaCcint
+to compile, install and work properly:
-Due to a bug in Cint 5.14.38 compilation will fail with GCC 2.95.2,
-maybe even with all 2.95.x. Currently you must use EGCS-1.1.x. This
-is under investigation.
+ Cint version | is known to work with | is known not to work with
+--------------+---------------------------+-----------------------------
+ < 5.14.37 | | (incompatible with GiNaC)
+ 5.14.38 | egcs 1.1.1 (problematic) | gcc.2.95.2
+ 5.14.39 | egcs 1.1.1, gcc.2.95.2 | gcc <= 2.7.2.3
+ 5.14.40 | egcs 1.1.1, gcc.2.95.2 | gcc <= 2.7.2.3