X-Git-Url: https://www.ginac.de/ginac.git//ginac.git?p=ginac.git;a=blobdiff_plain;f=INSTALL;h=4555857e83d9bc7f4afb3f18a8febb96bd3da2d5;hp=5e300b5e0252fc67a3e59efdc6414e7fa32deccb;hb=2c2f86ef17534853bc9b5e9c03229c5b57862d98;hpb=7d5599da087670e2ce1229789a847acd73fe8e0a diff --git a/INSTALL b/INSTALL index 5e300b5e..4555857e 100644 --- a/INSTALL +++ b/INSTALL @@ -1,10 +1,24 @@ Prerequisites ============= -GiNaC requires the CLN library by Bruno Haible, available at - or . -You will also need a C++ compiler adhering to the ANSI standard (we used gcc -for development so if you have a different compiler you are on your own). +GiNaC requires the CLN library by Bruno Haible, available at 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 C++ +interpreter cint (which requires that you register for commercial +use). 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 @@ -19,10 +33,7 @@ As with any autoconfiguring GNU software, installation is as easy as this: $ make install Known to work with: - - Linux/x86, EGCS-1.1.2 or GCC 2-95. - -The "make" step takes about 10 minutes, on a 586 DX / 133 MHz / 64 MB or -about 2 minutes on a P-III /550 MHz / 512 MB. + - Linux/x86, EGCS-1.1.2 or GCC 2-95.1/2-95.2 The "configure" script can be given a number of options to enable and disable various features. For a complete list, type: @@ -40,11 +51,33 @@ 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 +a P-III/500MHz with "enough" memory: + +step: | GCC optimization level: | comment: + | -O0 | -O1 | -O2 | +--------------+--------+--------+--------+------------------------------- +make | ~4m | ~6m | ~10m | building shared and static lib +make check | ~2m | ~2m | ~7m | mostly due to compilation + Problems with CLN ================= -You should use at least CLN V1.0.2, since all earlier ones are -somewhat buggy. Even V1.0.1 has a few problems and GiNaC will not -support older versions. Please install it properly on your system -before continuing with GiNaC. +You should use at least CLN V1.0.3, 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. + + +Working with the Cint C++ interpreter +===================================== + +You need to specify + --with-cint=$CINTSYSDIR +...