|
|
| version 1.2, 2002/01/31 11:11:43 | version 1.40, 2005/03/16 14:37:03 |
|---|---|
| Line 1 | Line 1 |
| 0.Assuming your perform your builds in $D directory | 0.Assuming your perform your builds in $HOME directory |
| and suggested subdirectories. | and suggested subdirectories. |
| 1.What is the process to compile Parser3? | 1.What is the process to compile Parser3? |
| As most UNIX libraries Parser3 follows the "standard": | 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 | |
| mkdir $D/parser3project | Then you can use these Parser3 configure options to specify the location and static/dynamic linkage with libgc: |
| cd $D/parser3project | --with-static-gc=$HOME/gc/lib |
| gunzip -c parser3src.xxx.tar.gz | tar xvf - | --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": | |
| mkdir $HOME/parser3project | |
| cd $HOME/parser3project | |
| gunzip -c parser3-x.x.tar.gz | tar xvf - | |
| mv parser3-x.x parser3 | |
| cd parser3 | cd parser3 |
| ./configure --prefix=/usr/local | ./configure --prefix=$HOME/parser3install --silent |
| make | make |
| That renaming is needed for SQL drivers to be able to find | |
| necessary include-file in Parser3 sources. | |
| NOTE: | |
| On some system you should run 'gmake'. | |
| NOTE: | |
| By default your would get 'parser3' binary without support of these features: | By default your would get 'parser3' binary without support of these features: |
| * cache(hashfile class) | |
| * xml(xdoc and xnode classes) | * xml(xdoc and xnode classes) |
| Read section (3) on getting xml-abled parser. | |
| Read section (4) on configure options. | |
| 2.What is the process to install Parser3? | 2.What is the process to install Parser3? |
| Line 23 | Line 53 |
| Installation layout: | Installation layout: |
| $prefix/bin/ | $prefix/bin/ |
| parser3 -- CGI and command line Parser3 interpreter | parser3 -- CGI and command line Parser3 interpreter |
| auto.p.dist -- configuration file sample, | |
| copy it to auto.p and adjust to your needs | |
| $prefix/etc/ | $prefix/etc/ |
| parser3.conf -- main configuration file | |
| parser3.charsets/ -- charset definition files | parser3.charsets/ -- charset definition files |
| windows-1251.cfg -- cyrillic charset [windows-1251 encoding] | |
| koi8-r.cfg -- cyrillic charset [KOI8-R encoding] | koi8-r.cfg -- cyrillic charset [KOI8-R encoding] |
| windows-1250.cfg -- central europian charset [windows-1250 encoding] | windows-1250.cfg -- central europian charset [windows-1250 encoding] |
| windows-1251.cfg -- cyrillic charset [windows-1251 encoding] | |
| windows-1257.cfg -- baltic charset [windows-1257 encoding] | |
| NOTE: | 3.What other libraries are needed to compile/install parser? |
| For subsequent compilations+installs | |
| to prevent configuration files to be overwritten use | |
| make install-exec | |
| it will update parser3 binary only. | |
| 2.What other libraries are needed to compile/install libxml ? | |
| * You can compile and use parser without any additional libraries. | |
| That would be 'basic' version of it. | |
| * In case you wish cache(hashfile class) support you need library | |
| libdb 2.x.x >= 2.7.7 | |
| on your system, and specify it to Parser3 configure script. | |
| Installation sequence of this library to $D/BerkeleyDB: | |
| cd db-2.x.x | |
| cd build_unix | |
| ../dist/configure --prefix=$D | |
| make install | |
| Parser3 configure option is --with-db2=$D/BerkeleyDB | |
| * 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.3.6 | libxml2 >= 2.6.5 [ftp://xmlsoft.org/libxml2-2.6.17.tar.gz] |
| libxslt >= 1.0.9 | libxslt >= 1.1.2 [ftp://xmlsoft.org/libxslt-1.1.10.tar.gz] |
| glib >= 1.2.10 | glib >= 1.2.10 [ftp://ftp.gtk.org/pub/gtk/v1.2/glib-1.2.10.tar.gz] |
| gdome2 >= 0.7.0 | 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. | on your system, and specify path to them to Parser3 configure script. |
| Sources of these two libraries must be patched prior to compile: | Sources of libgdome library must be patched prior to compile. [library author bug confirmation pending] |
| * libxml2 | |
| * libxslt | |
| Installation sequence of these libraries to $D/gnome: | Installation sequence of these libraries to $HOME/gnome: |
| libxml2: | libxml2: |
| cd libxml2-x.x.x | cd libxml2-x.x.x |
| patch -p0 < $D/parser3project/parser3/src/patches/libxml_error_column_tab.patch | ./configure --prefix=$HOME/gnome --without-zlib --without-iconv --without-threads --silent |
| patch -p0 < $D/parser3project/parser3/src/patches/libxml_htmloutput_of_xslemptyattr_emptyquotes.patch | |
| patch -p0 < $D/parser3project/parser3/src/patches/libxml_transcoder_context1.patch | |
| patch -p0 < $D/parser3project/parser3/src/patches/libxml_transcoder_context2.patch | |
| patch -p0 < $D/parser3project/parser3/src/patches/libxml_transcoder_context3.patch | |
| patch -p0 < $D/parser3project/parser3/src/patches/libxml_transcoder_context4.patch | |
| ./configure --prefix=$D/gnome | |
| make install | make install |
| libxslt: | libxslt: |
| cd libxslt-x.x.x | cd libxslt-x.x.x |
| patch -p0 < $D/parser3project/parser3/src/patches/libxslt_html_output_no_charset_meta.patch | ./configure --with-libxml-prefix=$HOME/gnome --prefix=$HOME/gnome --without-debug --without-debugger --silent |
| ./configure --with-libxml-prefix=$D/gnome --prefix=$D/gnome --without-debug --without-debugger | |
| make install | make install |
| glib: [ftp://ftp.gtk.org/pub/gtk/v1.2/glib-1.2.10.tar.gz] | glib: |
| cd glib-x.x.x | cd glib-x.x.x |
| ./configure --prefix=$D/gnome | ./configure --prefix=$HOME/gnome --silent |
| make install | make install |
| gdome2: | gdome2: |
| ./configure --with-glib-prefix=$D/gnome --disable-glibtest --with-libxml-prefix=$D/gnome --prefix=$D/gnome | 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 | make install |
| And patch+copy these additional headers into install includes directory | And copy these additional headers into install includes directory |
| patch -p0 < $D/parser3project/parser3/src/patches/libgdome_cpp_syntax1.patch | mkdir -p $HOME/gnome/include/libgdome/gdomecore |
| patch -p0 < $D/parser3project/parser3/src/patches/libgdome_cpp_syntax2.patch | cp libgdome/gdomecore/gdome-xml-node.h $HOME/gnome/include/libgdome/gdomecore |
| mkdir $D/gnome/include/libgdome/gdomecore | cp libgdome/gdomecore/gdome-xml-document.h $HOME/gnome/include/libgdome/gdomecore |
| cp libgdome/gdomecore/gdome-xml-node.h $D/gnome/include/libgdome/gdomecore | |
| cp libgdome/gdomecore/gdome-xml-document.h $D/gnome/include/libgdome/gdomecore | |
| Parser3 configure option is --with-gnome-xml=$D/gnome | Parser3 configure options, choose whether you need static or dynamic linkage with xml libs: |
| --with-static-xml=$HOME/gnome | |
| --with-shared-xml=$HOME/gnome | |
| NOTE: | |
| In case your glib as installed into some other prefix, | |
| specify it's configuration file with | |
| --with-glib-config=/path/to/your/glib-config | |
| NOTE: | |
| In case you are using SHARED xml libraries, you may want to link in direct path to them, | |
| use this key to specify which linker key to use do do that: | |
| --with-pathlink=LKEY put dynamic libraries paths to binary | |
| using linker key (-R, -rpath-link) | |
| 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/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. | |
| glib: | |
| cd glib-x.x.x | |
| ./configure --prefix=$HOME/gnome | |
| make install | |
| gmime: | |
| cd gmime-x.x.x | |
| ./configure --prefix=$HOME/gnome | |
| make install | |
| Parser3 configure options, choose whether you need static or dynamic linkage with xml libs: | |
| Alexandr Petrosian(PAF) <paf@design.ru> | --with-static-mailreceive=$HOME/gnome |
| --with-shared-mailreceive=$HOME/gnome | |
| NOTE: | |
| In case your glib as installed into some other prefix, | |
| specify it's configuration file with | |
| --with-glib-config=/path/to/your/glib-config | |
| NOTE: | |
| In case you are using SHARED mime library, you may want to link in direct path to it, | |
| use this key to specify which linker key to use do do that: | |
| --with-pathlink=LKEY put dynamic libraries paths to binary | |
| using linker key (-R, -rpath-link) | |
| 4. | |
| In case you're not root on machine you're installing Parser, | |
| we recommend you to do: | |
| ./configure --prefix=/your/home/parser3install | |
| 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 any exec operations by setting | |
| --disable-execs | |
| option to configure. | |
| file::exec, file::cgi and mail:send (unix version) methods would be disabled. | |
| You can enable reading and executing files, not belonging to group+user | |
| other then effective by setting | |
| --disable-safe-mode | |
| option to configure. | |
| You can disable user-configured sendmail commands by forcing it, setting | |
| "--with=sendmail=COMMAND" | |
| option to configure. | |
| In case you are experiencing problem with gcc runtime exception handling, | |
| try to configure with | |
| --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: | |
| --with-charsets=CHARSET[,CHARSET,...] Enables charsets in root config (windows-1251, | |
| windows-1250 windows-1257 koi8-r; Default is windows-1251) | |
| SQL clients: | |
| --with-mysql-client=mysqlclientlib?params | |
| --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 <any additional options to apache configure to pass> | |
| 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 <paf@design.ru> (http://paf.design.ru) | |
| $Id$ | $Id$ |