+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.
+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 <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
+=====================================
+
+The interface to the Cint C++ interpreter is currently in an alpha
+state. Please see <http://root.cern.ch/root/Cint.html> 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
+ $ ./configure --with-cint
+or specify it on the command line saying
+ $ ./configure --with-cint=/my/path/to/cintsysdir
+Good luck!
+
+ Known to work with: | Known not to work with:
+-----------------------+----------------------------
+ Cint 5.14.25 | Cint 5.14.24
+ Cint 5.14.26 | Cint 5.14.29