-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.