container.pl: can now generate constructors for an arbitary number

[ginac.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index f4d77cd6f85b7e07504e3ced431e3c9e28d4f277..aee07da74f0abe5517a6b1d5808b8e89d47a8d7b 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -1,4 +1,4 @@
-Prerequisites
+PREREQUISITES

 =============
 
 GiNaC requires the CLN library by Bruno Haible, available at either
 =============
 
 GiNaC requires the CLN library by Bruno Haible, available at either


@@ -21,7 +21,7 @@ distribution before trying to compile GiNaC-cint.  (See section
 `Working with the Cint C++ interpreter' below.)
 
 
 `Working with the Cint C++ interpreter' below.)
 
 

-Installation
+INSTALLATION

 ============
 
 As with any autoconfiguring GNU software, installation is as easy as this:
 ============
 
 As with any autoconfiguring GNU software, installation is as easy as this:


@@ -64,8 +64,11 @@ make          |  ~4m   |  ~6m   |  ~10m  | building shared and static lib
 make check    |  ~2m   |  ~2m   |  ~7m   | mostly due to compilation
 
 
 make check    |  ~2m   |  ~2m   |  ~7m   | mostly due to compilation
 
 

+COMMON PROBLEMS
+===============
+

 Problems with CLN
 Problems with CLN

-=================
+-----------------

 
 You should use at least CLN V1.0.3, since during the development of
 GiNaC various bugs have been discovered and fixed in earlier versions.
 
 You should use at least CLN V1.0.3, since during the development of
 GiNaC various bugs have been discovered and fixed in earlier versions.


@@ -74,6 +77,19 @@ 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.
 
 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 <ftp://ftp.gnu.org/gnu/readline/>
+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.
+

 
 Working with the Cint C++ interpreter
 =====================================
 
 Working with the Cint C++ interpreter
 =====================================


@@ -90,7 +106,7 @@ or specify it on the command line saying
  $ ./configure --with-cint=/my/path/to/cintsysdir
 Good luck!
 
  $ ./configure --with-cint=/my/path/to/cintsysdir
 Good luck!
 

-  Known to work with:  |  Known not to work with:   
+  Known to work with:  |  Known not to work with:

 -----------------------+----------------------------
 -----------------------+----------------------------

-  Cint 5.14.25         |  Cint 5.14.29              
-  Cint 5.14.26         |                            
+  Cint 5.14.25         |  Cint 5.14.24
+  Cint 5.14.26         |  Cint 5.14.29