X-Git-Url: https://www.ginac.de/ginac.git//ginac.git?p=ginac.git;a=blobdiff_plain;f=INSTALL;h=fadf8baeef4837b4e781ed156ec82f9d06c70c76;hp=0c629b5af7bea61732b3b0287de285abce88b41e;hb=c9282804ff4127fc84bb01b2b8707fbb6724b003;hpb=be6cad814c18ff39f4e16c32441e98e6d72f32d4 diff --git a/INSTALL b/INSTALL index 0c629b5a..fadf8bae 100644 --- a/INSTALL +++ b/INSTALL @@ -29,7 +29,7 @@ As with any autoconfiguring GNU software, installation is as easy as this: $ make $ make check [become root if necessary] - $ make install + # make install Known to work with: - Linux/x86, EGCS-1.1.x and GCC 2-95.x @@ -56,13 +56,13 @@ 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 -a P-III/500MHz with "enough" memory: +an Athlon/800MHz with "enough" memory: step: | GCC optimization level: | comment: | -O0 | -O1 | -O2 | --------------+--------+--------+--------+------------------------------- -make | ~4m | ~6m | ~10m | building shared and static lib -make check | ~3m | ~3m | ~7m | mostly due to compilation +make | ~4m | ~5m | ~6m | building shared and static lib +make check | ~20m | ~11m | ~12m | largely due to compilation COMMON PROBLEMS @@ -71,12 +71,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 ---------------------------- @@ -101,13 +100,15 @@ 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 GiNaCcint +Here is an overview to gives you an idea if you can expect GiNaC-cint to compile, install and work properly: - Cint version | is known to work with | is known not to work with ---------------+---------------------------+------------------------------ - < 5.14.39 | `verboten' by license (please bite your favorite lawyer) - 5.14.39 | egcs 1.1.1, gcc.2.95.2 | gcc <= 2.7.2.3 - 5.14.40 | egcs 1.1.1, gcc.2.95.2 | gcc <= 2.7.2.3 + 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-79 | compiles fine, works well with GCC 2.95.x. GCC3 no go.