X-Git-Url: https://www.ginac.de/ginac.git//ginac.git?p=ginac.git;a=blobdiff_plain;f=INSTALL;h=4d0cf1353b9b5eaa5a17bcf3387906337ba58ae5;hp=3be16c1fe03b0d68341b61cb9cbea84c2e0472cc;hb=acae7ab5a4dc94d1f54ba794f32f5764cdb4d704;hpb=4847adb5b4143c9ad9aff29d212a1656e59f02c1

diff --git a/INSTALL b/INSTALL
index 3be16c1f..4d0cf135 100644
--- a/INSTALL
+++ b/INSTALL
@@ -11,27 +11,28 @@ use the same compiler you compiled CLN with because of differing
 name-mangling schemes.
 
 The pkg-config utility is required for configuration, it can be downloaded
-from <http://pkg-config.freedesktop.org/>.
+from <http://pkg-config.freedesktop.org/>. Also Python version >= 2.6 is
+required.
 
 To build the GiNaC tutorial and reference manual the doxygen utility
 (it can be downloaded from http://www.stack.nl/~dimitri/doxygen) and
 TeX are necessary.
 
 Known to work with:
- - Linux on x86 and x86_64 using GCC 3.4, 4.0, 4.1, and 4.2.
- - Linux on Alpha using GCC 3.4.
- - Solaris on Sparc using GCC 3.4.
+ - Linux on x86 and x86_64 using 
+   - GCC 3.4, 4.0, 4.1, 4.2, 4.3.x (x >= 1), 4.4, 4.5, 4.6, and 4.9
+   - Clang 2.8
  - Windows on x86 using GCC 3.4 (MinGW)
 
 Known not to work with:
+ - Clang 2.7 and earlier due to poor C++ support.
  - GCC 4.3.0 due to the compiler bug,
    see <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35548>.
  - GCC 2.96 or earlier because proper exception and standard library support
    is missing there.
 
 If you install from git, you also need GNU autoconf (>=2.59), automake (>=1.8),
-libtool (>= 1.5), bison (>= 2.3), flex (>= 2.5.33), autogen (>= 5.6.0) to be
-installed.
+libtool (>= 1.5), python (>= 2.5), bison (>= 2.3), flex (>= 2.5.33) to be installed.
 
 
 INSTALLATION
@@ -74,17 +75,16 @@ A few of the more important ones:
 More detailed installation instructions can be found in the documentation,
 in the doc/ directory.
 
-The time the "make" step takes depends heavily on optimization levels. Large
-amounts of memory (>128MB) will be required by the compiler, 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:
+The time the "make" step takes depends on optimization levels. To give you
+a rough idea of what you have to expect the following table may be helpful.
+It was measured on an Athlon X2/3GHz with 4Gb of RAM.
 
 step          | GCC optimization  | comment
               |   -O1   |   -O2   |
 --------------+---------+---------+----------------------------------------
-make          |   ~6m   |   ~8m   | shared and static library
-make check    |   ~8m   |  ~12m   | largely due to compilation
+make          |   ~1m   |   ~2m   | shared library only (--disable-static),
+              |         |         | parallel compilation (MAKEFLAGS=-j2)
+make check    |   ~6m   |   ~6m   | largely due to compilation
 
 
 To install from git