X-Git-Url: https://www.ginac.de/ginac.git//ginac.git?p=ginac.git;a=blobdiff_plain;f=INSTALL;h=e1881a352da25f57fa739eedcc963ce0ef735cc7;hp=ee1eb2b078956ad5c5f2cdfe1dfb8922a9d3f96d;hb=3db194853d3dd2719231b83e4956cf6bcbe53627;hpb=8d21b348c9a5ab3445d00c3e797dd7f67153ef45

diff --git a/INSTALL b/INSTALL
index ee1eb2b0..e1881a35 100644
--- a/INSTALL
+++ b/INSTALL
@@ -6,11 +6,11 @@ one of the following FTP-sites:
   * <ftp://ftp.santafe.edu/pub/gnu/>,
   * <ftp://ftp.ilog.fr/pub/Users/haible/gnu/> or
   * <ftp://ftpthep.physik.uni-mainz.de/pub/gnu/>.
-You will also need a decent ANSI-compliant C++-compiler.  We use
-`post-EGCS' GCC, i.e GCC >= 2.95 for development so if you have a
-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.
+You will also need a decent ANSI-compliant C++-compiler.  We recommend
+the C++ compiler from the GNU compiler collection, GCC >= 3.0.  If you
+have a different or older 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.
 
 
 INSTALLATION
@@ -25,9 +25,10 @@ As with any autoconfiguring GNU software, installation is as easy as this:
  # make install
 
 Known to work with:
-  - Linux on x86, Alpha and Sparc using GCC 2-95.x.
+  - Linux on x86, Alpha and Sparc using GCC 3.0.x, 3.1 and 3.2.
 Known not to work with:
-  - GCC 2.7.x or earlier because proper exception support is missing there.
+  - GCC 2.96 or earlier because proper exception and standard library support
+    is missing there.
 
 The "configure" script can be given a number of options to enable and
 disable various features. For a complete list, type:
@@ -51,11 +52,11 @@ also depending on optimization.  To give you a rough idea of what you
 have to expect the following table may be helpful.  It was measured on
 an Athlon/800MHz with "enough" memory:
 
-step:         | GCC optimization level:  | comment:
-              |  -O0   |  -O1   |  -O2   |
---------------+--------+--------+--------+-------------------------------
-make          |   ~4m  |   ~5m  |   ~6m  | building shared and static lib
-make check    |  ~20m  |  ~11m  |  ~12m  | largely due to compilation
+step          | GCC optimization  | comment
+              |   -O1   |   -O2   |
+--------------+---------+---------+----------------------------------------
+make          |   ~6m   |   ~8m   | shared and static library
+make check    |   ~8m   |  ~12m   | largely due to compilation
 
 
 COMMON PROBLEMS
@@ -67,8 +68,7 @@ Problems with CLN
 You should use at least CLN-1.1, since during the development of
 GiNaC various bugs have been discovered and fixed in earlier versions.
 Please install CLN properly on your system before continuing with
-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.
+GiNaC.
 
 Problems with building ginsh
 ----------------------------
@@ -80,13 +80,10 @@ 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.
 
-Problems with missing <sstream>
--------------------------------
+Problems with missing standard header files
+-------------------------------------------
 
-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>.
+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.