-and compile it yourself. After that it should work fine.
-
-
-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
+and compile it yourself.
+
+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>.