<ul>
<li>Linux ELF on i386 with gcc 2.95, gcc 3.0, gcc 3.1, and Intel ICC 5.0
and 6.0;
- <li>Sun Solaris 2.5, 2.6, 7, and 8 on Sparc, with gcc 2.95,
+ <li>Sun Solaris 2.5, 2.6, 7, 8, and 9 on Sparc, with gcc 2.95,
gcc 3.0, and gcc 3.1;
- <li>Sun Solaris 2.9 on Sparc in 64bit mode, with gcc 3.1.1;
+ <li>Sun Solaris 9 on Sparc in 64bit mode, with gcc 3.1.1;
<li>Sun Solaris 8 on i386, with gcc 2.95;
<li>FreeBSD 4.5 with gcc 2.95;
<li>IBM AIX 4.2, with gcc 2.95 (with some restrictions on
<li> <p>
Previous versions of the library supported generation of
printable documentation. However, due to the size (around
- 2000 pages) which refrains most people from printing, and
+ 4000 pages) which refrains most people from printing, and
the high cost of supporting this option, we dropped the
possibility of printable documentation.
</p>
<p>
To execute one of the commands, type `make target-name'. Please
note that building all libraries in debug and optimized mode
- presently takes about two hours on a Sun Ultra 450 (with 250 MHz),
+ presently takes about three hours on a Sun Ultra 450 (with 250 MHz),
or about half an hour on a Pentium IV 1000 Mhz, so you may want to do
this during lunchtime or night. Also, note that building all
libraries requires 200-400 MB of free disk space (depending on
minimize cross-dependencies, this speeds up compilation by about
the factor given after `-j', at least if you have as many
processors. Note, however, that parallel makes will sometimes fail
- when compiling the library for the first time (this is due to a
+ when compiling the library for the very first time (this is due to a
bug in `make'); in that case, simply re-run `make', or run it
without `-jN'.
</p>
<p>
Besides the debugging output the compiler puts into the output,
the library contains a great number of assertions (presently
- about 2700) checking the validity of parameters to functions and
+ about 3200) checking the validity of parameters to functions and
internal states. These assertions have proven to be an
- invaluable mean to finding programming bugs since they will
+ invaluable means to finding programming bugs since they will
almost always abort your program if something goes wrong. In our
experience, more than ninety per cent of all errors are invalid
parameters (such as vectors having the wrong size, etc) and they