X-Git-Url: https://www.ginac.de/ginac.git//ginac.git?p=ginac.git;a=blobdiff_plain;f=INSTALL;h=7c6258f3889723389732d7913c2cab8e3b229589;hp=a401b4c75fec5c0bc3a004179e3c6593f9334442;hb=de552105d0e4304d869f3d88729b34a613a11b45;hpb=2db71ba580988a98abad7dba06bd7927f878fe38 diff --git a/INSTALL b/INSTALL index a401b4c7..7c6258f3 100644 --- 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. -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.) - INSTALLATION ============ @@ -32,7 +25,7 @@ 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 2-95.x. Known not to work with: - GCC 2.7.x or earlier because proper exception support is missing there. @@ -58,11 +51,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 @@ -71,12 +64,11 @@ COMMON PROBLEMS 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. -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 -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 ---------------------------- @@ -88,30 +80,18 @@ libreadline and maybe libreadline-dev. If your system's vendor doesn't supply such packages, go to and compile it yourself. - -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.41 | 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-52 | compiles fine, works well +Problems with missing standard header files +------------------------------------------- + +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. If the only file missing is , however, there is +a solution. GCC-2.95.2 and earlier don't ship with this file. A +working implementation has been available since GCC-2.95.3. GCC-3.0 +and later have an even better, fully standard-conforming +implementation, by default. If you are stuck with GCC-2.95.2 or +earlier and you cannot upgrade your compiler we recommend obtaining +the libstdc++-v2 header written by Magnus Fromreide. It was +posted to the gcc-patches mailing list on November 21 2000: +.