-
-Working with the Cint C++ interpreter
-=====================================
-
-Please see <http://root.cern.ch/root/Cint.html> 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
-Enjoy!
-
-Here is an overview to gives you an idea if you can expect GiNaCcint
-to compile, install and work properly:
-
- 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
+Problems with missing standard header files
+-------------------------------------------
+
+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. If the only file missing is <sstream>, however, there is
+a solution. GCC-2.95.2 and earlier don't ship with this file. A
+working implementation has been available since GCC-2.95.3. GCC-3.0
+and later have an even better, fully standard-conforming
+implementation, by default. If you are stuck with GCC-2.95.2 or
+earlier and you cannot upgrade your compiler we recommend obtaining
+the libstdc++-v2 <sstream> header written by Magnus Fromreide. It was
+posted to the gcc-patches mailing list on November 21 2000:
+<http://gcc.gnu.org/ml/gcc-patches/2000-11/msg01152.html>.