File: install-unix.html

package info (click to toggle)
php3 3%3A3.0.18-0potato1.1
links: PTS
area: main
in suites: potato
size: 17,736 kB
ctags: 11,198
sloc: ansic: 108,120; sh: 2,512; php: 2,024; yacc: 1,887; makefile: 1,038; perl: 537; pascal: 238; awk: 90; cpp: 28; sql: 11
file content (2187 lines) | stat: -rw-r--r-- 36,206 bytes
parent folder | download | duplicates (3)
<HTML
><HEAD
><TITLE
>Installation on UNIX systems</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.56"><LINK
REL="HOME"
TITLE="PHP Manual"
HREF="manual.html"><LINK
REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
HREF="installation.html"><LINK
REL="NEXT"
TITLE="Installation on Windows 95/98/NT systems"
HREF="install-windows95-nt.html"><META
NAME="HTTP_EQUIV"
CONTENT="text/html; charset=ISO-8859-1"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PHP Manual</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="installation.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 2. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="install-windows95-nt.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="install-unix"
>Installation on UNIX systems</A
></H1
><P
>&#13;    This section will guide you through the configuration and
    installation of PHP.  Prerequisite knowledge and software:
    
    <P
></P
><UL
><LI
><P
>&#13;       Basic UNIX skills (being able to operate "make" and a C
       compiler)
      </P
></LI
><LI
><P
>&#13;       An ANSI C compiler
      </P
></LI
><LI
><P
>&#13;       A web server
      </P
></LI
></UL
>
   </P
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN138"
>Quick Installation Instructions (Apache Module Version)</A
></H2
><P
>&#13;     <DIV
CLASS="informalexample"
><P
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="programlisting"
>&#13;1.  gunzip apache_1.3.x.tar.gz
2.  tar xvf apache_1.3.x.tar
3.  gunzip php-x.x.x.tar.gz
4.  tar xvf php-x.x.x.tar
5.  cd apache_1.3.x
6.  ./configure --prefix=/www
7.  cd ../php-x.x.x
8.  ./configure --with-mysql --with-apache=../apache_1.3.x --enable-track-vars
9.  make
10. make install
11. cd ../apache_1.3.x
12. for PHP 3: ./configure --activate-module=src/modules/php3/libphp3.a
    for PHP 4: ./configure --activate-module=src/modules/php4/libphp4.a
13. make
14. make install

  Instead of this step you may prefer to simply copy the httpd binary
  overtop of your existing binary.  Make sure you shut down your
  server first though.

15. cd ../php-x.x.x
16. for PHP 3: cp php3.ini-dist /usr/local/lib/php3.ini
    for PHP 4: cp php.ini-dist /usr/local/lib/php.ini

  You can edit your .ini file to set PHP options.  If
  you prefer this file in another location, use
  --with-config-file-path=/path in step 8.

17. Edit your httpd.conf or srm.conf file and add: 
      
     For PHP 3:   AddType application/x-httpd-php3 .php3
     For PHP 4:   AddType application/x-httpd-php .php
 
  You can choose any extension you wish here.  .php is simply the one
  we suggest. You can even include .html .


18. Use your normal procedure for starting the Apache server. (You must
    stop and restart the server, not just cause the server to reload by
    use a HUP or USR1 signal.)
      </PRE
></TD
></TR
></TABLE
><P
></P
></DIV
>
    </P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="with-apache"
>Apache Module</A
></H2
><P
>&#13;     PHP can be compiled in a number of different ways. Here is a
     quick summary:
     <DIV
CLASS="informalexample"
><P
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="programlisting"
>&#13;./configure --with-apxs --with-pgsql
      </PRE
></TD
></TR
></TABLE
><P
></P
></DIV
>
    </P
><P
>&#13;     This will create a <TT
CLASS="filename"
>libphp4.so</TT
> shared library
     that is loaded into Apache using a LoadModule line in Apache's
     <TT
CLASS="filename"
>httpd.conf</TT
> file. The PostgreSQL support is
     embedded into this <TT
CLASS="filename"
>libphp4.so</TT
> library.
    </P
><P
>&#13;     <DIV
CLASS="informalexample"
><P
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="programlisting"
>&#13;./configure --with-apxs --with-pgsql=shared
      </PRE
></TD
></TR
></TABLE
><P
></P
></DIV
>
    </P
><P
>&#13;     This will again create a <TT
CLASS="filename"
>libphp4.so</TT
> shared
     library for Apache, but it will also create a
     <TT
CLASS="filename"
>pgsql.so</TT
> shared library that is loaded into
     PHP either by using the extension directive in
     <TT
CLASS="filename"
>php.ini</TT
> file or by loading it explicitly in
     a script using the <A
HREF="function.dl.html"
><B
CLASS="function"
>dl()</B
></A
> function.
    </P
><P
>&#13;     <DIV
CLASS="informalexample"
><P
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="programlisting"
>&#13;./configure --with-apache=/path/to/apache_source --with-pgsql
      </PRE
></TD
></TR
></TABLE
><P
></P
></DIV
>
    </P
><P
>&#13;     This will create a <TT
CLASS="filename"
>libmodphp4.a</TT
> library, a
     <TT
CLASS="filename"
>mod_php4.c</TT
> and some accompanying files and
     copy this into the <TT
CLASS="literal"
>src/modules/php4</TT
> directory
     in the Apache source tree. Then you compile Apache using
     <TT
CLASS="literal"
>--activate-module=src/modules/php4/libphp4.a</TT
>
     and the Apache build system will create
     <TT
CLASS="filename"
>libphp4.a</TT
> and link it statically into the
     <TT
CLASS="filename"
>httpd</TT
> binary. The PostgreSQL support is
     included directly into this <TT
CLASS="filename"
>httpd</TT
> binary, so
     the final result here is a single <TT
CLASS="filename"
>httpd</TT
>
     binary that includes all of Apache and all of PHP.
    </P
><P
>&#13;     <DIV
CLASS="informalexample"
><P
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="programlisting"
>&#13;./configure --with-apache=/path/to/apache_source --with-pgsql=shared
      </PRE
></TD
></TR
></TABLE
><P
></P
></DIV
>
    </P
><P
>&#13;     Same as before, except instead of including PostgreSQL support
     directly into the final <TT
CLASS="filename"
>httpd</TT
> you will get a
     <TT
CLASS="filename"
>pgsql.so</TT
> shared library that you can load
     into PHP from either the <TT
CLASS="filename"
>php.ini</TT
> file or
     directly using <A
HREF="function.dl.html"
><B
CLASS="function"
>dl()</B
></A
>.
    </P
><P
>&#13;     When choosing to build PHP in different ways, you should consider
     the advantages and drawbacks of each method. Building as a shared
     object will mean that you can compile apache separately, and don't
     have to recompile everything as you add to, or change, PHP.
     Building PHP into apache (static method) means that PHP will
     load and run faster. For more information, see the Apache
     <A
HREF="http://www.apache.org/docs/dso.html"
TARGET="_top"
>webpage on DSO support</A
>.
    </P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="with-fhttpd"
>fhttpd Module</A
></H2
><P
>&#13;     To build PHP as an fhttpd module, answer "yes" to "Build as an
     fhttpd module?" (the <TT
CLASS="option"
><A
HREF="install-unix.html#with-fhttpd"
>&#13;     --with-fhttpd</A
>=<TT
CLASS="replaceable"
><I
>DIR</I
></TT
></TT
>
     option to configure) and specify the fhttpd source base
     directory.  The default directory is <TT
CLASS="filename"
>/usr/local/src/fhttpd</TT
>. If you are
     running fhttpd, building PHP as a module will give better
     performance, more control and remote execution
     capability.
    </P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="install-cgi"
>CGI version</A
></H2
><P
>&#13;     The default is to build PHP as a CGI program.  If you are
     running a web server PHP has module support for, you should
     generally go for that solution for performance reasons.  However,
     the CGI version enables Apache users to run different
     PHP-enabled pages under different user-ids.  Please make sure
     you read through the <A
HREF="security.html"
>Security
     chapter</A
> if you are going to run PHP as a CGI.
    </P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="database-support-options"
>Database Support Options</A
></H2
><P
>&#13;     PHP has native support for a number of databases (as well as
     ODBC):
    </P
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-adabas"
>Adabas D</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-adabas<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enables Adabas D support.  The parameter is the Adabas D
      install directory and defaults to <TT
CLASS="filename"
>/usr/local/adabasd</TT
>.
     </P
><P
>&#13;      <A
HREF="http://www.adabas.com/"
TARGET="_top"
>Adabas home page</A
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-dbase"
>dBase</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-dbase</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enables the bundled DBase support.  No external libraries are
      required.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-filepro"
>filePro</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-filepro</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enables the bundled read-only filePro support.  No external
      libraries are required.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-ibm-db2"
>IBM DB2</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-ibm-db2<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enables IBM DB2 support.  The parameter to this option is the 
      DB2 base install directory and defaults to 
      <TT
CLASS="filename"
>/home/db2inst1/sqllib</TT
>.
     </P
><P
>&#13;      <A
HREF="http://www.ibm.com/db2/"
TARGET="_top"
>IBM DB2 home page</A
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-msql"
>mSQL</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-msql<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enables mSQL support.  The parameter to this option is the mSQL
      install directory and defaults to <TT
CLASS="filename"
>/usr/local/Hughes</TT
>.  This is the
      default directory of the mSQL 2.0 distribution.
      <B
CLASS="command"
>configure</B
> automatically detects which mSQL
      version you are running and PHP supports both 1.0 and 2.0, but
      if you compile PHP with mSQL 1.0, you can only access mSQL 1.0
      databases, and vice-versa.
     </P
><P
>&#13;      See also <A
HREF="configuration.html#ini.sect.msql"
>mSQL Configuration</A
>
      Directives in the <A
HREF="configuration.html#configuration.file"
>configuration
      file</A
>.
     </P
><P
>&#13;      <A
HREF="http://www.hughes.com.au/"
TARGET="_top"
>mSQL home page</A
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-mysql"
>MySQL</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-mysql<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enables MySQL support.  The parameter to this option is the
      MySQL install directory and defaults to <TT
CLASS="filename"
>/usr/local</TT
>.  This is the default
      installation directory of the MySQL distribution.
     </P
><P
>&#13;      See also <A
HREF="configuration.html#ini.sect.mysql"
>MySQL
      Configuration</A
> Directives in the <A
HREF="configuration.html#configuration.file"
>configuration file</A
>.
     </P
><P
>&#13;      <A
HREF="http://www.mysql.com/"
TARGET="_top"
>MySQL home page</A
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-iodbc"
>iODBC</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-iodbc<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Includes iODBC support.  This feature was first developed for
      iODBC Driver Manager, a freely redistributable ODBC driver
      manager which runs under many flavors of UNIX. The parameter to
      this option is the iODBC installation directory and defaults to
      <TT
CLASS="filename"
>/usr/local</TT
>.</P
><P
>&#13;      <A
HREF="http://users.ids.net/~bjepson/freeODBC/"
TARGET="_top"
>FreeODBC home page</A
> 
      or <A
HREF="http://www.iodbc.org/"
TARGET="_top"
>iODBC home page</A
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-openlink"
>OpenLink ODBC</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-openlink<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Includes OpenLink ODBC support. The parameter to this option is
      the OpenLink ODBC installation directory and defaults to
      <TT
CLASS="filename"
>/usr/local/openlink</TT
>.
     </P
><P
>&#13;      <A
HREF="http://www.openlinksw.com/"
TARGET="_top"
>OpenLink Software's home
      page</A
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-oracle"
>Oracle</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-oracle<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Includes Oracle support.  Has been tested and should be working
      at least with Oracle versions 7.0 through 7.3.  The parameter is
      the <TT
CLASS="envar"
>ORACLE_HOME</TT
> directory.  You do not have to
      specify this parameter if your Oracle environment has been set
      up.</P
><P
>&#13;      <A
HREF="http://www.oracle.com/"
TARGET="_top"
>Oracle home page</A
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-pgsql"
>PostgreSQL</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-pgsql<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Includes PostgreSQL support.  The parameter is the PostgreSQL
      base install directory and defaults to <TT
CLASS="filename"
>/usr/local/pgsql</TT
>.
     </P
><P
>&#13;      See also <A
HREF="configuration.html#ini.sect.pgsql"
>Postgres
      Configuration</A
> Directives in the <A
HREF="configuration.html#configuration.file"
>configuration file</A
>.
     </P
><P
>&#13;      <A
HREF="http://www.postgresql.org/"
TARGET="_top"
>PostgreSQL home
      page</A
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-solid"
>Solid</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-solid<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Includes Solid support.  The parameter is the Solid install
      directory and defaults to <TT
CLASS="filename"
>/usr/local/solid</TT
>.
     </P
><P
>&#13;      <A
HREF="http://www.solidtech.com/"
TARGET="_top"
>Solid home page</A
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-sybase"
>Sybase</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-sybase<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Includes Sybase support.  The parameter is the Sybase install
      directory and defaults to <TT
CLASS="filename"
>/home/sybase</TT
>.
     </P
><P
>&#13;      See also <A
HREF="configuration.html#ini.sect.sybase"
>Sybase
      Configuration</A
> Directives in the <A
HREF="configuration.html#configuration.file"
>configuration file</A
>.
     </P
><P
>&#13;      <A
HREF="http://www.sybase.com/"
TARGET="_top"
>Sybase home page</A
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-sybase-ct"
>Sybase-CT</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-sybase-ct<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Includes Sybase-CT support.  The parameter is the Sybase-CT
      install directory and defaults to <TT
CLASS="filename"
>/home/sybase</TT
>.
     </P
><P
>&#13;      See also <A
HREF="configuration.html#ini.sect.sybct"
>Sybase-CT
      Configuration</A
> Directives in the <A
HREF="configuration.html#configuration.file"
>configuration
      file</A
>.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-velocis"
>Velocis</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-velocis<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Includes Velocis support.  The parameter is the Velocis install
      directory and defaults to <TT
CLASS="filename"
>/usr/local/velocis</TT
>.
     </P
><P
>&#13;      <A
HREF="http://www.raima.com/"
TARGET="_top"
>Velocis home page</A
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-custom-odbc"
>A custom ODBC library</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-custom-odbc<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Includes support for an arbitrary custom ODBC library.  The
      parameter is the base directory and defaults to <TT
CLASS="filename"
>/usr/local</TT
>.
     </P
><P
>&#13;      This option implies that you have defined CUSTOM_ODBC_LIBS when
      you run the configure script. You also must have a valid odbc.h
      header somewhere in your include path. If you don't have one,
      create it and include your specific header from there. Your
      header may also require some extra definitions, particularly
      when it is multiplatform. Define them in CFLAGS.</P
><P
>&#13;      For example, you can use Sybase SQL Anywhere on QNX as
      following:
      <TT
CLASS="literal"
>&#13;       CFLAGS=-DODBC_QNX LDFLAGS=-lunix CUSTOM_ODBC_LIBS="-ldblib
       -lodbc" ./configure --with-custom-odbc=/usr/lib/sqlany50
      </TT
>
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="disable-unified-odbc"
>Unified ODBC</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--disable-unified-odbc</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Disables the Unified ODBC module, which is a common interface to
      all the databases with ODBC-based interfaces, such as Solid, 
      IBM DB2 and Adabas D.  It also works for normal ODBC libraries. 
      Has been tested with iODBC, Solid, Adabas D, IBM DB2 and Sybase SQL
      Anywhere. Requires that one (and only one) of these modules or
      the Velocis module is enabled, or a custom ODBC library
      specified. This option is only applicable if one of the
      following options is used: <A
HREF="install-unix.html#with-iodbc"
>--with-iodbc</A
>, <A
HREF="install-unix.html#with-solid"
>--with-solid</A
>, <A
HREF="install-unix.html#with-ibm-db2"
>--with-ibm-db2</A
>, <A
HREF="install-unix.html#with-adabas"
>--with-adabas</A
>, <A
HREF="install-unix.html#with-velocis"
>--with-velocis</A
>, or <A
HREF="install-unix.html#with-custom-odbc"
>--with-custom-odbc</A
>.
     </P
><P
>&#13;      See also <A
HREF="configuration.html#ini.sect.uodbc"
>Unified ODBC
      Configuration</A
> Directives in the <A
HREF="configuration.html#configuration.file"
>configuration
      file</A
>.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-ldap"
>LDAP</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-ldap<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Includes <SPAN
CLASS="acronym"
>LDAP</SPAN
> (Lightweight Directory Access
      Protocol) support.  The parameter is the LDAP base install
      directory, defaults to <TT
CLASS="filename"
>/usr/local/ldap</TT
>.
     </P
><P
>&#13;      More information about LDAP can be found in <A
HREF="http://www.faqs.org/rfcs/rfc1777.html"
TARGET="_top"
>RFC1777</A
> and
      <A
HREF="http://www.faqs.org/rfcs/rfc1778.html"
TARGET="_top"
>RFC1778</A
>.
     </P
></DIV
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN364"
>Other configure options</A
></H2
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-mcrypt"
>--with-mcrypt<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-mcrypt</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Include support for the mcrypt library. See the <A
HREF="ref.mcrypt.html"
>mcrypt documentation</A
> for more
      information. If you use the optional
      <TT
CLASS="replaceable"
><I
>DIR</I
></TT
> argument, PHP will look for
      mcrypt.h in <TT
CLASS="replaceable"
><I
>DIR</I
></TT
>/include.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-sysvsem"
>--enable-sysvsem</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-sysvsem</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Include support for Sys V semaphores (supported by most Unix
      derivates). See the <A
HREF="ref.sem.html"
>Semaphore and Shared
      Memory documentation</A
> for more information.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-sysvshm"
>--enable-sysvshm</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-sysvshm</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Include support for Sys V shared memory (supported by most Unix
      derivates). See the <A
HREF="ref.sem.html"
>Semaphore and Shared
      Memory documentation</A
> for more information.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-xml"
>--with-xml</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-xml</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Include support for a non-validating XML parser using James
      Clark's <A
HREF="http://www.jclark.com/xml/"
TARGET="_top"
>expat library</A
>.  See the
      <A
HREF="ref.xml.html"
>XML function reference</A
> for
      details.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-maintainer-mode"
>--enable-maintainer-mode</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-maintainer-mode</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Turns on extra dependencies and compiler warnings used by some
      of the PHP developers.</P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-system-regex"
>--with-system-regex</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-system-regex</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Uses the system's regular expression library rather than the
      bundled one.  If you are building PHP as a server module, you
      must use the same library when building PHP as when linking the
      server.  Enable this if the system's library provides special
      features you need.  It is recommended that you use the bundled
      library if possible.</P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-config-file-path"
>--with-config-file-path</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-config-file-path=DIR</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      The path used to look for <A
HREF="configuration.html#configuration.file"
>the
      configuration file</A
> when PHP starts up.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="with-exec-dir"
>--with-exec-dir</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--with-exec-dir<TT
CLASS="replaceable"
><I
>=DIR</I
></TT
></TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Only allow running of executables in DIR when in safe mode.
      Defaults to <TT
CLASS="filename"
>/usr/local/bin</TT
>.
      This option only sets the default, it may be changed with the
      <A
HREF="configuration.html#ini.safe-mode-exec-dir"
>safe_mode_exec_dir</A
>
      directive in the <A
HREF="configuration.html#configuration.file"
>configuration
      file</A
> later.</P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-debug"
>--enable-debug</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-debug</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enables extra debug information. This makes it possible to
      gather more detailed information when there are problems with
      PHP.  (Note that this doesn't have anything to do with debugging
      facilities or information available to PHP scripts.)
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-safe-mode"
>--enable-safe-mode</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-safe-mode</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enables "safe mode" by default. This imposes several
      restrictions on what PHP can do, such as opening only files
      within the document root.  Read the <A
HREF="security.html"
>Security chapter</A
> for more more
      information.  CGI users should always enable secure mode.  This
      option only sets the default, it may be enabled or disabled with
      the <A
HREF="configuration.html#ini.safe-mode"
>safe_mode</A
> directive in
      the <A
HREF="configuration.html#configuration.file"
>configuration file</A
>
      later.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-track-vars"
>--enable-track-vars</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-track-vars</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Makes PHP keep track of where GET/POST/cookie variables come
      from in the arrays HTTP_GET_VARS, HTTP_POST_VARS and
      HTTP_COOKIE_VARS.  This option only sets the default, it may be
      enabled or disabled with the <A
HREF="configuration.html#ini.track-vars"
>track_vars</A
> directive in the
      <A
HREF="configuration.html#configuration.file"
>configuration file</A
>
      later.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-magic-quotes"
>--enable-magic-quotes</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-magic-quotes</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enable magic quotes by default.  This option only sets the
      default, it may be enabled or disabled with the <A
HREF="configuration.html#ini.magic-quotes-runtime"
>magic_quotes_runtime</A
>
      directive in the <A
HREF="configuration.html#configuration.file"
>configuration file</A
>
      later. See also the <A
HREF="configuration.html#ini.magic-quotes-gpc"
>&#13;      magic_quotes_gpc</A
> and the <A
HREF="configuration.html#ini.magic-quotes-sybase"
>magic_quotes_sybase</A
>
      directives.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-debugger"
>--enable-debugger</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-debugger</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enables the internal PHP debugger support.  This feature is
      still in an experimental state. See also the <A
HREF="configuration.html#ini.sect.debugger"
>Debugger Configuration</A
>
      directives in the <A
HREF="configuration.html#configuration.file"
>configuration
      file</A
>.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-discard-path"
>--enable-discard-path</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-discard-path</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      If this is enabled, the PHP CGI binary can safely be placed
      outside of the web tree and people will not be able to
      circumvent .htaccess security.  Read the <A
HREF="security.html#security.cgi.shell"
>section in the security
      chapter</A
> about this option.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-bcmath"
>--enable-bcmath</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-bcmath</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enables <B
CLASS="command"
>bc</B
> style arbitrary precision math
      functions. See also the <A
HREF="configuration.html#ini.sect.bcmath"
>bcmath.scale </A
> option in the
      <A
HREF="configuration.html#configuration.file"
>configuration
      file</A
>.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-force-cgi-redirect"
>--enable-force-cgi-redirect</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-force-cgi-redirect</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Enable the security check for internal server redirects.  You
      should use this if you are running the CGI version with
      Apache.
     </P
><P
>&#13;      When using PHP as a CGI binary, PHP by default always first
      checks that it is used by redirection (for example under Apache,
      by using Action directives).  This makes sure that the PHP
      binary cannot be used to bypass standard web server
      authentication procedures by calling it directly, like <TT
CLASS="filename"
>http://my.host/cgi-bin/php/secret/doc.html</TT
>.
      This example accesses <TT
CLASS="filename"
>http://my.host/secret/doc.html</TT
> but does
      not honour any security settings enforced by httpd for directory
      <TT
CLASS="filename"
>/secret</TT
>.
     </P
><P
>&#13;      Not enabling option disables the check and enables bypassing
      httpd security and authentication settings.  Do this only if
      your server software is unable to indicate that a safe
      redirection was done and all your files under your document root
      and user directories may be accessed by anyone.
     </P
><P
>&#13;      Read the <A
HREF="security.html#security.cgi.force-redirect"
>section in
      the security chapter</A
> about this option.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="disable-short-tags"
>--disable-short-tags</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--disable-short-tags</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Disables the short form <TT
CLASS="literal"
>&#60;? ?&#62;</TT
> PHP tags.
      You must disable the short form if you want to use PHP with
      <SPAN
CLASS="acronym"
>XML</SPAN
>.  With short tags disabled, the only PHP
      code tag is <TT
CLASS="literal"
>&#60;?php ?&#62;</TT
>.  This option only
      sets the default, it may be enabled or disabled with the <A
HREF="configuration.html#ini.short-open-tag"
>short_open_tag</A
> directive in
      the <A
HREF="configuration.html#configuration.file"
>configuration file</A
>
      later.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="enable-url-includes"
>--enable-url-includes</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--enable-url-includes</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Makes it possible to run code on other HTTP or FTP servers
      directly from PHP with <A
HREF="function.include.html"
>include()</A
>.  See also the <A
HREF="configuration.html#ini.include-path"
>include_path</A
> option in the
      <A
HREF="configuration.html#configuration.file"
>configuration file</A
>.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="disable-syntax-hl"
>--disable-syntax-hl</A
></H3
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="synopsis"
>&#13;      <TT
CLASS="option"
>--disable-syntax-hl</TT
>
     </PRE
></TD
></TR
></TABLE
><P
>&#13;      Turns off syntax highlighting.
     </P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="AEN504"
>CPPFLAGS and LDFLAGS</A
></H3
><P
>&#13;      To make the PHP installation look for header or library files in
      different directories, modify the <TT
CLASS="envar"
>CPPFLAGS</TT
> and
      <TT
CLASS="envar"
>LDFLAGS</TT
> environment variables, respectively.  If
      you are using a sensible shell, you should be able to do
      <B
CLASS="command"
>&#13;       LDFLAGS=-L/my/lib/dir CPPFLAGS=-I/my/include/dir ./configure
      </B
>
     </P
></DIV
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN510"
>Building</A
></H2
><P
>&#13;     When PHP is configured, you are ready to build the CGI executable
     or the PHP library.  The command <B
CLASS="command"
>make</B
> should
     take care of this.  If it fails and you can't figure out why, see
     the <A
HREF="install-problems.html"
>Problems section</A
>.
    </P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN515"
>Testing</A
></H2
><P
>&#13;     If you have built PHP as a CGI program, you may test your build
     by typing <B
CLASS="command"
>make test</B
>.  It is always a good idea
     to test your build.  This way you may catch a problem with PHP on
     your platform early instead of having to struggle with it later.
    </P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN519"
>Benchmarking</A
></H2
><P
>&#13;     If you have built PHP as a CGI program, you may benchmark your
     build by typing <B
CLASS="command"
>make bench</B
>. Note that if safe
     mode is on by default, the benchmark may not be able to finish if
     it takes longer then the 30 seconds allowed. This is because the
     <A
HREF="function.set-time-limit.html"
><B
CLASS="function"
>set_time_limit()</B
></A
> can not be used in safe
     mode. Use the <A
HREF="configuration.html#ini.max-execution-time"
>max_execution_time</A
>
     configuration setting to control this time for your own
     scripts. <B
CLASS="command"
>make bench</B
> ignores the <A
HREF="configuration.html#configuration.file"
>configuration file</A
>.
    </P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="installation.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="manual.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="install-windows95-nt.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Installation</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installation.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Installation on Windows 95/98/NT systems</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>