PREREQUISITES
=============
-GiNaC requires the CLN library by Bruno Haible, available at either
-one of the following FTP-sites:
- * <ftp://ftp.santafe.edu/pub/gnu/>,
- * <ftp://ftp.ilog.fr/pub/Users/haible/gnu/> or
- * <ftp://ftpthep.physik.uni-mainz.de/pub/gnu/>.
-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
- * <ftp://root.cern.ch/root/>.
-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 <ftp://ftpthep.physik.uni-mainz.de/pub/gnu/>.
+
+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
$ 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
+ - Linux on x86, Alpha and Sparc using GCC 3.0.x, 3.1 and 3.2.
+Known not to work with:
+ - GCC 2.96 or earlier because proper exception and standard library support
+ is missing there.
+
+To build the GiNaC tutorial and reference manual in HTML, DVI, PostScript,
+or PDF formats, use one of
+
+ $ make html
+ $ make dvi
+ $ make ps
+ $ make pdf
The "configure" script can be given a number of options to enable and
disable various features. For a complete list, type:
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
[defaults to the value given to --prefix]
--disable-shared suppress the creation of a shared version of libginac
+ --disable-static suppress the creation of a static version of libginac
More detailed installation instructions can be found in the documentation,
in the doc/ directory.
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
+step | GCC optimization | comment
+ | -O1 | -O2 |
+--------------+---------+---------+----------------------------------------
+make | ~6m | ~8m | shared and static library
+make check | ~8m | ~12m | largely due to compilation
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.
your system/distribution is, you will have to install a package called
libreadline and maybe libreadline-dev. If your system's vendor
doesn't supply such packages, go to <ftp://ftp.gnu.org/gnu/readline/>
-and compile it yourself. After that it should work fine.
-
-If you want to build a completely static ginsh and your compiler still
-complains about unresolved objects try linking with libncurses, too.
-
-
-Working with the Cint C++ interpreter
-=====================================
-
-Please see <http://root.cern.ch/root/Cint.html> 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
-Enjoy!
-
-Here is an overview to gives you an idea if you can expect GiNaCcint
-to compile, install and work properly:
-
- Cint version | is known to work with | is known not to work with
---------------+---------------------------+-----------------------------
- < 5.14.37 | | (incompatible with GiNaC)
- 5.14.38 | egcs 1.1.1 (problematic) | gcc.2.95.2
- 5.14.39 | egcs 1.1.1, gcc.2.95.2 | gcc <= 2.7.2.3
+and compile it yourself.
+
+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.
git://www.ginac.de / ginac.git / blobdiff