--- parser3/INSTALL	2003/04/03 15:34:01	1.31.6.2
+++ parser3/INSTALL	2003/07/24 11:31:18	1.33
@@ -1,7 +1,20 @@
 0.Assuming your perform your builds in $HOME directory 
   and suggested subdirectories.
 
-1.What is the process to compile Parser3? 
+1.What is the process to compile Parser3?
+
+  First, you must have LIBGC installed (conservative garbage collector for C++).
+      libgc >= 6.1 [http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.1.tar.gz]
+    
+    Installation sequence of this library to $HOME/gc:
+
+    cd libgc-x.x
+    ./configure --prefix=$HOME/gc --disable-threads --silent
+    make install
+
+    Then you can use these Parser3 configure options to specify the location and static/dynamic linkage with libgc:
+        --with-static-gc=$HOME/gc/lib
+        --with-shared-gc=$HOME/gc/lib
 
   As most UNIX programs Parser3 follows the "standard":
 
@@ -45,30 +58,15 @@
 
 3.What other libraries are needed to compile/install parser? 
 
-3a. First, you must install LIBGC (conservative garbage collector for C++). 
-      libgc >= 1.6 [http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.1.tar.gz]
-    That would be 'basic' version of it.
-    
-    Without any options configure script would try to test whether linker could find it itself.
-
-
-    Installation sequence of this library to $HOME/gc:
-
-    cd libgc-x.x
-    ./configure --prefix=$HOME/gc --silent
-    make install
-
-    Then you can use these Parser3 configure options to specify the location and static/dynamic linkage with libgc:
-        --with-static-gc=$HOME/gc/lib
-        --with-shared-gc=$HOME/gc/lib
-
-3b. In case you wish XML(xdoc and xnode classes) support, you need libraries
+3a. In case you wish XML(xdoc and xnode classes) support, you need libraries
       libxml2 >= 2.5.5 [ftp://xmlsoft.org/libxml2-2.5.5.tar.gz]
       libxslt >= 1.0.28 [ftp://xmlsoft.org/libxslt-1.0.28.tar.gz]
       glib >= 1.2.10 [ftp://ftp.gtk.org/pub/gtk/v1.2/glib-1.2.10.tar.gz]
       gdome2 >= 0.7.4 [http://gdome2.cs.unibo.it/tarball/gdome2-0.7.4.tar.gz]
     on your system, and specify path to them to Parser3 configure script.
 
+    Sources of libgdome library must be patched prior to compile. [library author bug confirmation pending]
+
     Installation sequence of these libraries to $HOME/gnome:
 
     libxml2:
@@ -92,6 +90,7 @@
     gdome2:
 
     cd gdome2-x.x.x
+    patch -p0 < $HOME/parser3project/parser3/src/lib/patches/gdome2.patch
     ./configure --with-glib-prefix=$HOME/gnome --disable-glibtest --with-libxml-prefix=$HOME/gnome --prefix=$HOME/gnome --silent
     make install
 
@@ -116,7 +115,7 @@
         --with-pathlink=LKEY    put dynamic libraries paths to binary
                                 using linker key (-R, -rpath-link)
 
-3c. In case you wish $mail:receive support you need libraries
+3b. In case you wish $mail:receive support you need libraries
       glib >= 1.2.10 [ftp://ftp.gtk.org/pub/gtk/v1.2/glib-1.2.10.tar.gz]
       gmime >= 1.0.1 [http://spruce.sourceforge.net/gmime/sources/gmime-1.0.5.tar.gz]
     on your system, and specify path to them to Parser3 configure script.
@@ -157,10 +156,6 @@
   and afterwards copy parser3install/bin/parser3 to your CGI directory
   or make a symlink [if your web server configured to follow symlinks].
 
-  You can disable libstdc++ linkage by setting
-  --disable-link-libstdcpp
-  option to configure.  
-
   You can disable any exec operations by setting
   --disable-execs
   option to configure.
@@ -180,6 +175,11 @@
   --with-sjlj-exceptions
   option.  
 
+  By default libstdc++ is linked statically, you can re-enable dynamic libstdc++ linkage by specifying
+  --with-dynamic-stdcpp
+  option to configure.  
+
+
   Some root config options can be specified at configure time, and would override autodetects.
 
   List of enabled charsets:
@@ -193,4 +193,4 @@
  
 Alexandr Petrosian <paf@design.ru> (http://paf.design.ru)
 
-$Id: INSTALL,v 1.31.6.2 2003/04/03 15:34:01 paf Exp $
+$Id: INSTALL,v 1.33 2003/07/24 11:31:18 paf Exp $