- Explain what's going on with <sstream>.

[ginac.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index 584801e3410afc68fd6b3a655242084f13d54e67..ee1eb2b078956ad5c5f2cdfe1dfb8922a9d3f96d 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -12,13 +12,6 @@ different compiler you are on your own.  Note that you may have to use
 the same compiler you compiled CLN with because of differing
 name-mangling schemes.
 
 the same compiler you compiled CLN with because of differing
 name-mangling schemes.
 

-Optionally, GiNaC may work together with Masaharu Goto's free C++
-interpreter Cint.  You may obtain it from
-  * <ftp://root.cern.ch/root/>.
-Install it by following the instructions included in Cint's
-distribution before trying to compile GiNaC-cint.  (See section
-`Working with the Cint C++ interpreter' below.)
-

 
 INSTALLATION
 ============
 
 INSTALLATION
 ============


@@ -29,10 +22,10 @@ As with any autoconfiguring GNU software, installation is as easy as this:
  $ make
  $ make check
 [become root if necessary]
  $ make
  $ make check
 [become root if necessary]

- $ make install
+ # make install

 
 Known to work with:
 
 Known to work with:

-  - Linux/x86, EGCS-1.1.x and GCC 2-95.x
+  - Linux on x86, Alpha and Sparc using GCC 2-95.x.

 Known not to work with:
   - GCC 2.7.x or earlier because proper exception support is missing there.
 
 Known not to work with:
   - GCC 2.7.x or earlier because proper exception support is missing there.
 


@@ -71,12 +64,11 @@ COMMON PROBLEMS
 Problems with CLN
 -----------------
 
 Problems with CLN
 -----------------
 

-You should use at least CLN V1.0.3, since during the development of
+You should use at least CLN-1.1, since during the development of

 GiNaC various bugs have been discovered and fixed in earlier versions.
 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
 Please install CLN properly on your system before continuing with

-GiNaC.
+GiNaC.  When using GCC3 as compiler please use at least CLN-1.1.1
+since some parts of GiNaC won't build with CLN-1.1.

 
 Problems with building ginsh
 ----------------------------
 
 Problems with building ginsh
 ----------------------------


@@ -88,30 +80,13 @@ 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.
 
 doesn't supply such packages, go to <ftp://ftp.gnu.org/gnu/readline/>
 and compile it yourself.
 

+Problems with missing <sstream>
+-------------------------------

 
 

-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.39,40 | 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    | compiles fine, still some weirdnesses during execution
+GCC-2.95.2 and earlier don't have support for this header.  GiNaC can use
+<strstream> instead, but this may cause some trouble later.  GCC-3.0 has a
+completely new implementation of the STL-headers (libstdc++-v3) and there,
+standard-conforming support for <sstream> is present.  If you can't upgrade
+your compiler we recommend using the libstdc++-v2 <sstream> header 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>.