-
-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
-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.41 | compiles but does not feel happy at all (inconsistent!)
- 5.14.41 | tested on egcs 1.1.1, gcc 2.95.2: some weirdnesses
- 5.14.44 | does not compile: G__cpp_ginaccint.C needs manual fixes
- 5.14.45-56 | compiles fine, works well
+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>.