Diff for /parser3/INSTALL between versions 1.11 and 1.31.6.2

version 1.11, 2002/03/11 11:02:57 version 1.31.6.2, 2003/04/03 15:34:01
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 programs Parser3 follows the "standard":    As most UNIX programs Parser3 follows the "standard":
   
   mkdir $D/parser3project    mkdir $HOME/parser3project
   cd $D/parser3project    cd $HOME/parser3project
   gunzip -c parser3-x.x.tar.gz | tar xvf -    gunzip -c parser3-x.x.tar.gz | tar xvf -
   mv parser3-x.x parser3    mv parser3-x.x parser3
   cd parser3    cd parser3
Line 24 Line 24
         * xml(xdoc and xnode classes)          * xml(xdoc and xnode classes)
   Read section (3) on getting xml-abled parser.    Read section (3) on getting xml-abled parser.
   
   NOTE:   
   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].  
   
   NOTE:    Read section (4) on configure options.
   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.  
     
   NOTE:  
   You can disable reading of files, belonging to group   
   other then current  by setting  
   --disable-forein-group-files  
   option to configure.  
     
   
 2.What is the process to install Parser3?  2.What is the process to install Parser3?
   
Line 51 Line 34
   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
         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-1251.cfg  -- cyrillic charset [windows-1251 encoding]
         windows-1257.cfg  -- baltic charset [windows-1257 encoding]          windows-1257.cfg  -- baltic charset [windows-1257 encoding]
   
   NOTE:  
     For subsequent compilations+installs   
     to prevent configuration files to be overwritten use  
     
     make install-exec  
       
     it will update parser3 binary only.  
   
 3.What other libraries are needed to compile/install parser?   3.What other libraries are needed to compile/install parser? 
   
   * You can compile and use parser without any additional libraries.  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.      That would be 'basic' version of it.
       
       Without any options configure script would try to test whether linker could find it itself.
   
   
   * In case you wish xml(xdoc and xnode classes) support you need libraries      Installation sequence of this library to $HOME/gc:
       libxml2 >= 2.3.6  
       libxslt >= 1.0.9  
       glib >= 1.2.10  
       gdome2 >= 0.7.0  
     on your system, and specify path to them to Parser3 configure script.  
   
     Sources of these two libraries must be patched prior to compile:       cd libgc-x.x
       * libxml2      ./configure --prefix=$HOME/gc --silent
       * libxslt      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]
       on your system, and specify path to them to Parser3 configure script.
   
     Installation sequence of these libraries to $D/gnome:      Installation sequence of these libraries to $HOME/gnome:
   
     libxml2:  [ftp://ftp.gnome.org/pub/GNOME/stable/sources/libxml/libxml2-2.4.12.tar.gz]      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 --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 --without-zlib  
     make install      make install
   
     libxslt:  [ftp://ftp.gnome.org/pub/GNOME/stable/sources/libxslt/libxslt-1.0.9.tar.gz]      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 
     make install      make install
   
     gdome2:  [http://phd.cs.unibo.it/gdome2/tarball/gdome2-0.7.0.tar.gz]      gdome2:
   
     cd gdome2-x.x.x      cd gdome2-x.x.x
         patch -p0 < $D/parser3project/parser3/src/patches/libgdome_cpp_syntax1.patch      ./configure --with-glib-prefix=$HOME/gnome --disable-glibtest --with-libxml-prefix=$HOME/gnome --prefix=$HOME/gnome --silent
         patch -p0 < $D/parser3project/parser3/src/patches/libgdome_cpp_syntax2.patch  
         patch -p0 < $D/parser3project/parser3/src/patches/libgdome_morestatic.patch  
     ./configure --with-glib-prefix=$D/gnome --disable-glibtest --with-libxml-prefix=$D/gnome --prefix=$D/gnome  
     make install      make install
   
     And copy these additional headers into install includes directory      And copy these additional headers into install includes directory
   
     mkdir $D/gnome/include/libgdome/gdomecore      mkdir $HOME/gnome/include/libgdome/gdomecore
     cp libgdome/gdomecore/gdome-xml-node.h $D/gnome/include/libgdome/gdomecore      cp libgdome/gdomecore/gdome-xml-node.h $HOME/gnome/include/libgdome/gdomecore
     cp libgdome/gdomecore/gdome-xml-document.h $D/gnome/include/libgdome/gdomecore      cp libgdome/gdomecore/gdome-xml-document.h $HOME/gnome/include/libgdome/gdomecore
           
   
     Parser3 configure options, choose whether you need static or dynamic linkage with xml libs:      Parser3 configure options, choose whether you need static or dynamic linkage with xml libs:
         --with-static-xml=$D/gnome          --with-static-xml=$HOME/gnome
         --with-shared-xml=$D/gnome          --with-shared-xml=$HOME/gnome
   
     NOTE:      NOTE:
     In case your glib as installed into some other prefix,      In case your glib as installed into some other prefix,
     specify it's configuration file with      specify it's configuration file with
         --with-glib-config=/path/to/your/glib-config          --with-glib-config=/path/to/your/glib-config
         NOTE:      NOTE:
         In case you are using SHARED xml libraries, you may want to link in direct path to them,      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:      use this key to specify which linker key to use do do that:
         --with-pathlink=LKEY    put dynamic libraries paths to binary          --with-pathlink=LKEY    put dynamic libraries paths to binary
                                 using linker key (-R, -rpath-link)                                  using linker key (-R, -rpath-link)
   
   3c. 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.
   
       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:
           --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 libstdc++ linkage by setting
     --disable-link-libstdcpp
     option to configure.  
   
     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.  
   
     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
     
     
 Alexandr Petrosian <paf@design.ru> (http://paf.design.ru)  Alexandr Petrosian <paf@design.ru> (http://paf.design.ru)
   

Removed from v.1.11  
changed lines
  Added in v.1.31.6.2


E-mail: