X-Git-Url: https://www.ginac.de/ginac.git//ginac.git?p=ginac.git;a=blobdiff_plain;f=INSTALL;h=f5d6635dd4e29db599b2b49530736f33879f4c67;hp=551b5995236ddb6fea8a433f0e0e17d1d30a2591;hb=73081e1cccfec32a9e9dab6a5e4b063b3fa0e7fb;hpb=4c347efb39a3a53ff1e814227e513f6b31a43c44
diff --git a/INSTALL b/INSTALL
index 551b5995..f5d6635d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,23 +1,14 @@
PREREQUISITES
=============
-GiNaC requires the CLN library by Bruno Haible, available from either
-one of the following FTP-sites:
- * ,
- * or
- * .
-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.
-
-Optionally, GiNaC may work together with Masaharu Goto's free C++
-interpreter Cint. You may obtain it from
- * .
-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.)
+GiNaC requires the CLN library by Bruno Haible installed on your system.
+It is available from .
+
+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
@@ -32,9 +23,10 @@ As with any autoconfiguring GNU software, installation is as easy as this:
# make install
Known to work with:
- - Linux/x86, EGCS-1.1.x and 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:
@@ -58,11 +50,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
@@ -74,8 +66,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
----------------------------
@@ -87,30 +78,10 @@ libreadline and maybe libreadline-dev. If your system's vendor
doesn't supply such packages, go to
and compile it yourself.
+Problems with missing standard header files
+-------------------------------------------
-Working with the Cint C++ interpreter
-=====================================
-
-Please see 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.60 | since GiNaC version 0.7, these do not compile any more
- 5.14.62-72 | compiles fine, works well with GCC 2.95.x. GCC3 no go.
- 5.14.74 | requires defining -DG__LONGBUF in SYSMACRO and OTHMACRO.
- 5.14.75-76 | compiles fine, works well with GCC 2.95.x. GCC3 no go.
+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.