--- parser3/INSTALL 2003/04/11 07:44:44 1.31.6.3 +++ parser3/INSTALL 2005/03/16 14:37:03 1.40 @@ -1,7 +1,26 @@ 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.4.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 + + NOTE: + On some platforms there is special version of libgc patched to support some + local piece of subtlety. + Official libgc does not work there, use special version instead. + (OpenBSD reported to be one of those) As most UNIX programs Parser3 follows the "standard": @@ -10,7 +29,7 @@ gunzip -c parser3-x.x.tar.gz | tar xvf - mv parser3-x.x parser3 cd parser3 - ./configure --prefix=/usr/local + ./configure --prefix=$HOME/parser3install --silent make That renaming is needed for SQL drivers to be able to find @@ -45,28 +64,12 @@ 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 - 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] +3a. In case you wish XML(xdoc and xnode classes) support, you need libraries + libxml2 >= 2.6.5 [ftp://xmlsoft.org/libxml2-2.6.17.tar.gz] + libxslt >= 1.1.2 [ftp://xmlsoft.org/libxslt-1.1.10.tar.gz] + glib >= 1.2.10 [ftp://ftp.gtk.org/pub/gtk/v1.2/glib-1.2.10.tar.gz] + on freebsd5 this is reported to work: ftp://ftp.gtk.org/pub/gtk/v1.1/glib-1.1.16.tar.gz + gdome2 >= 0.7.4 [http://gdome2.cs.unibo.it/tarball/gdome2-0.8.1.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] @@ -76,7 +79,7 @@ libxml2: cd libxml2-x.x.x - ./configure --prefix=$HOME/gnome --without-zlib --without-iconv --silent + ./configure --prefix=$HOME/gnome --without-zlib --without-iconv --without-threads --silent make install libxslt: @@ -88,7 +91,7 @@ glib: cd glib-x.x.x - ./configure --prefix=$HOME/gnome + ./configure --prefix=$HOME/gnome --silent make install gdome2: @@ -100,7 +103,7 @@ And copy these additional headers into install includes directory - mkdir $HOME/gnome/include/libgdome/gdomecore + mkdir -p $HOME/gnome/include/libgdome/gdomecore cp libgdome/gdomecore/gdome-xml-node.h $HOME/gnome/include/libgdome/gdomecore cp libgdome/gdomecore/gdome-xml-document.h $HOME/gnome/include/libgdome/gdomecore @@ -119,9 +122,9 @@ --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] + gmime >= 1.0.1 [http://spruce.sourceforge.net/gmime/sources/v1.0/gmime-1.0.8.tar.gz] on your system, and specify path to them to Parser3 configure script. You may have already installed glib at 3b step. @@ -160,10 +163,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. @@ -183,6 +182,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,7 +197,20 @@ --with-pgsql-client=pgsqlclientlib?params --with-oracle-client=oracleclientlib?params - +5. + If you need to build apache 1.3 parser module, get source distribution of apache 1.3, + run configure there, then run parser configure with one more option: + --with-apache13=Apache13 source distribution directory + after 'make' go to that directory and run + + ./p3runConfigure + + example: + ./p3runConfigure --prefix=$D/apache13install --enable-module=rewrite + + WARNING: if you want to use apache configure option --enable-shared=max, do this: + ./p3runConfigure --enable-shared=max --disable-shared=mod_parser3.c + Alexandr Petrosian (http://paf.design.ru) -$Id: INSTALL,v 1.31.6.3 2003/04/11 07:44:44 paf Exp $ +$Id: INSTALL,v 1.40 2005/03/16 14:37:03 paf Exp $