Sophie

Sophie

distrib > Mandriva > 9.1 > ppc > media > main > by-pkgid > 0afeee9cca140e167a996902b9a677c5 > files > 35

php-manual-en-4.3.0-2mdk.noarch.rpm

<HTML
><HEAD
><TITLE
>Build Problems</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="PHP Manual"
HREF="index.html"><LINK
REL="UP"
TITLE="FAQ: Frequently Asked Questions"
HREF="faq.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
HREF="faq.installation.html"><LINK
REL="NEXT"
TITLE="Using PHP"
HREF="faq.using.html"><META
HTTP-EQUIV="Content-type"
CONTENT="text/html; charset=ISO-8859-1"></HEAD
><BODY
CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="faq.installation.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="faq.using.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="chapter"
><H1
><A
NAME="faq.build"
>Chapter 49. Build Problems</A
></H1
><P
>&#13;    This section gathers most common errors that occur at 
    build time.
   </P
><DIV
CLASS="qandaset"
><DL
><DT
>1. <A
HREF="faq.build.html#faq.build.configure"
>&#13;      I got the latest version of PHP using the anonymous CVS service, 
      but there's no configure script!
     </A
></DT
><DT
>2. <A
HREF="faq.build.html#faq.build.configuring"
>&#13;      I'm having problems configuring PHP to work with Apache. 
      It says it can't find <TT
CLASS="filename"
>httpd.h</TT
>, but it's right where I said it is!
     </A
></DT
><DT
>3. <A
HREF="faq.build.html#faq.build.lex"
>&#13;      While configuring PHP (<TT
CLASS="literal"
>./configure</TT
>), you come across
      an error similar to the following:
     </A
></DT
><DT
>4. <A
HREF="faq.build.html#faq.build.apache-sharedcore"
>&#13;      When I try to start Apache, I get the the following
      message:
     </A
></DT
><DT
>5. <A
HREF="faq.build.html#faq.build.not-found"
>&#13;      When I run configure, it says that it can't find the 
      include files or library for GD, gdbm, or some other package!
     </A
></DT
><DT
>6. <A
HREF="faq.build.html#faq.build.yytname"
>&#13;      When it is compiling the file <TT
CLASS="filename"
>language-parser.tab.c</TT
>, it gives me errors 
      that say <TT
CLASS="literal"
>yytname undeclared</TT
>.
     </A
></DT
><DT
>7. <A
HREF="faq.build.html#faq.build.link"
>&#13;      When I run <B
CLASS="command"
>make</B
>, it seems to run fine but then fails when it tries 
      to link the final application complaining that it can't find some files.
     </A
></DT
><DT
>8. <A
HREF="faq.build.html#faq.build.undefined"
>&#13;      When linking PHP, it complains about a number of undefined references.
     </A
></DT
><DT
>9. <A
HREF="faq.build.html#faq.build.Apache"
>&#13;      I can't figure out how to build PHP with Apache 1.3.
     </A
></DT
><DT
>10. <A
HREF="faq.build.html#faq.build.not-running"
>&#13;      I have followed all the steps to install the Apache module version on 
      UNIX, and my PHP scripts show up in my browser or I am being asked to 
      save the file.
     </A
></DT
><DT
>11. <A
HREF="faq.build.html#faq.build.activate-module"
>&#13;      It says to use: <TT
CLASS="literal"
>--activate-module=src/modules/php4/libphp4.a</TT
>, 
      but  that file doesn't exist, so I changed it to 
      <TT
CLASS="literal"
>--activate-module=src/modules/php4/libmodphp4.a</TT
> and it 
      doesn't work!? What's going on?
     </A
></DT
><DT
>12. <A
HREF="faq.build.html#faq.build.ansi"
>&#13;      When I try to build Apache with PHP as a static module using 
      <TT
CLASS="literal"
>--activate-module=src/modules/php4/libphp4.a</TT
> 
      it tells me that my compiler is not ANSI compliant.
     </A
></DT
><DT
>13. <A
HREF="faq.build.html#faq.build.apxs"
>&#13;      When I try to build PHP using <TT
CLASS="literal"
>--with-apxs</TT
>
      I get strange error messages.
     </A
></DT
><DT
>14. <A
HREF="faq.build.html#faq.build.microtime"
>&#13;     During <B
CLASS="command"
>make</B
>, I get errors in microtime, and a lot of <TT
CLASS="literal"
>RUSAGE_</TT
> stuff.
    </A
></DT
><DT
>15. <A
HREF="faq.build.html#faq.build.upgrade"
>&#13;      I want to upgrade my PHP. Where can I find the <B
CLASS="command"
>./configure</B
>
      line that was used to build my current PHP installation?
     </A
></DT
><DT
>16. <A
HREF="faq.build.html#faq.build.gdlibs"
>&#13;      When building PHP with the GD library it either gives strange compile errors
      or segfaults on execution.
     </A
></DT
></DL
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.configure"
></A
><B
>1. </B
>
      I got the latest version of PHP using the anonymous CVS service, 
      but there's no configure script!
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      You have to have the GNU autoconf package installed so you can
      generate the configure script from <TT
CLASS="filename"
>configure.in</TT
>. Just run
      <B
CLASS="command"
>./buildconf</B
> in the top-level directory after getting
      the sources from the CVS server. (Also, unless you run configure
      with the <TT
CLASS="literal"
>--enable-maintainer-mode</TT
> option, the
      configure script will not automatically get rebuilt when the
      <TT
CLASS="filename"
>configure.in</TT
> file is updated, so you should make sure to do that
      manually when you notice configure.in has changed. One symptom
      of this is finding things like @VARIABLE@ in your Makefile after
      configure or <TT
CLASS="filename"
>config.status</TT
> is run.)
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.configuring"
></A
><B
>2. </B
>
      I'm having problems configuring PHP to work with Apache. 
      It says it can't find <TT
CLASS="filename"
>httpd.h</TT
>, but it's right where I said it is!
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      You need to tell the configure/setup script the location of the
      top-level of your Apache source tree. This means that
      you want to specify <TT
CLASS="literal"
>--with-apache=/path/to/apache</TT
>
      and <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>not</I
></SPAN
> <TT
CLASS="literal"
>--with-apache=/path/to/apache/src</TT
>.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.lex"
></A
><B
>3. </B
>
      While configuring PHP (<TT
CLASS="literal"
>./configure</TT
>), you come across
      an error similar to the following:
     </P
><P
>&#13;      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="screen"
>checking lex output file root... ./configure: lex: command not found
       configure: error: cannot find output from lex; giving up</PRE
></TD
></TR
></TABLE
>
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      Be sure to read the <A
HREF="install.unix.html"
>installation</A
>
      instructions carefully and note that you need both flex and bison
      installed to compile PHP.  Depending on your setup you will install 
      bison and flex from either source or a package, such as a RPM.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.apache-sharedcore"
></A
><B
>4. </B
>
      When I try to start Apache, I get the the following
      message:
     </P
><P
>&#13;      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="screen"
>fatal: relocation error: file /path/to/libphp4.so:
       symbol ap_block_alarms: referenced symbol not found</PRE
></TD
></TR
></TABLE
>
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      This error usually comes up when one compiles the Apache
      core program as a DSO library for shared usage.  Try to
      reconfigure apache, making sure to use at least the
      following flags:
     </P
><P
>&#13;      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="screen"
>--enable-shared=max --enable-rule=SHARED_CORE</PRE
></TD
></TR
></TABLE
>
     </P
><P
>&#13;      For more information, read the top-level Apache
      <TT
CLASS="filename"
>INSTALL</TT
> file or the Apache
      <A
HREF="http://httpd.apache.org/docs/dso.html"
TARGET="_top"
>DSO manual page</A
>.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.not-found"
></A
><B
>5. </B
>
      When I run configure, it says that it can't find the 
      include files or library for GD, gdbm, or some other package!
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      You can make the configure script looks for header files and libraries
      in non-standard locations by specifying additional flags to pass to
      the C preprocessor and linker, such as:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>CPPFLAGS=-I/path/to/include LDFLAGS=-L/path/to/library ./configure</PRE
></TD
></TR
></TABLE
>
      If you're using a csh-variant for your login shell (why?), it would be:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>env CPPFLAGS=-I/path/to/include LDFLAGS=-L/path/to/library ./configure</PRE
></TD
></TR
></TABLE
>
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.yytname"
></A
><B
>6. </B
>
      When it is compiling the file <TT
CLASS="filename"
>language-parser.tab.c</TT
>, it gives me errors 
      that say <TT
CLASS="literal"
>yytname undeclared</TT
>.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
       You need to update your version of Bison. You can find the latest version
       at <A
HREF="ftp://ftp.gnu.org/pub/gnu/bison/"
TARGET="_top"
>ftp://ftp.gnu.org/pub/gnu/bison/</A
>.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.link"
></A
><B
>7. </B
>
      When I run <B
CLASS="command"
>make</B
>, it seems to run fine but then fails when it tries 
      to link the final application complaining that it can't find some files.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      Some old versions of make that don't correctly put the compiled
      versions of the files in the functions directory into that same
      directory. Try running <B
CLASS="command"
>cp *.o functions</B
> and then
      re-running <B
CLASS="command"
>make</B
> to see if that helps. If it does, you should really
      upgrade to a recent version of GNU make.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.undefined"
></A
><B
>8. </B
>
      When linking PHP, it complains about a number of undefined references.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      Take a look at the link line and make sure that all of the appropriate  
      libraries are being included at the end. Common ones that you might have
      missed are '-ldl' and any libraries required for any database support
      you included.
     </P
><P
>&#13;      If you're linking with Apache 1.2.x, did you remember to add the
      appropriate information to the EXTRA_LIBS line of the Configuration
      file and re-rerun Apache's Configure script? See the 
      <A
HREF="http://cvs.php.net/co.php/php4/INSTALL"
TARGET="_top"
>INSTALL</A
> file that
      comes with the distribution for more information.
     </P
><P
>&#13;      Some people have also reported that they had to add '-ldl' immediately
      following <TT
CLASS="filename"
>libphp4.a</TT
> when linking with Apache.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.Apache"
></A
><B
>9. </B
>
      I can't figure out how to build PHP with Apache 1.3.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      This is actually quite easy.  Follow these steps carefully:
      <P
></P
><UL
><LI
><P
>&#13;         Grab the latest Apache 1.3 distribution from 
         <A
HREF="http://www.apache.org/dist/"
TARGET="_top"
>http://www.apache.org/dist/</A
>.
        </P
></LI
><LI
><P
>&#13;         Ungzip and untar it somewhere, for example 
         <TT
CLASS="filename"
>/usr/local/src/apache-1.3</TT
>.
        </P
></LI
><LI
><P
>&#13;         Compile PHP by first running 
         <B
CLASS="command"
>./configure --with-apache=/&#60;path&#62;/apache-1.3</B
>
         (substitute &#60;path&#62; for the actual path to your apache-1.3 directory.
        </P
></LI
><LI
><P
>&#13;         Type <B
CLASS="command"
>make</B
> followed by <B
CLASS="command"
>make install</B
>
         to build PHP and copy the necessary files to the Apache distribution tree.
        </P
></LI
><LI
><P
>&#13;         Change directories into to your <TT
CLASS="filename"
>/&#60;path&#62;/apache-1.3/src</TT
>
         directory and edit the <TT
CLASS="filename"
>Configuration</TT
> file. 
         Add to the file: 
         <TT
CLASS="literal"
>AddModule modules/php4/libphp4.a</TT
>.
        </P
></LI
><LI
><P
>&#13;         Type: <B
CLASS="command"
>./Configure</B
> followed by <TT
CLASS="literal"
>make</TT
>.
        </P
></LI
><LI
><P
>&#13;         You should now have a PHP-enabled httpd binary!
        </P
></LI
></UL
>
     </P
><P
>&#13;      <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>Note:</I
></SPAN
> You can also use the new Apache 
      <TT
CLASS="literal"
>./configure</TT
> script. See the instructions in 
      the <TT
CLASS="literal"
>README.configure</TT
> file which is part of 
      your Apache distribution.  Also have a look at the <TT
CLASS="filename"
>INSTALL</TT
> 
      file in the PHP distribution.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.not-running"
></A
><B
>10. </B
>
      I have followed all the steps to install the Apache module version on 
      UNIX, and my PHP scripts show up in my browser or I am being asked to 
      save the file.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      This means that the PHP module is not getting invoked for some reason.
      Three things to check before asking for further help:
      <P
></P
><UL
><LI
><P
>&#13;         Make sure that the httpd binary you are running is the actual 
         new httpd binary you just built.  To do this, try running: 
         <TT
CLASS="literal"
>/path/to/binary/httpd -l</TT
>
        </P
><P
>&#13;         If you don't see <TT
CLASS="filename"
>mod_php4.c</TT
> listed then
         you are not running the right binary.  Find and install the
         correct binary.
        </P
></LI
><LI
><P
>&#13;         Make sure you have added the correct Mime Type to one of your 
         <TT
CLASS="literal"
>Apache .conf</TT
> files.  It should be: 
         <TT
CLASS="literal"
>AddType application/x-httpd-php3 .php3</TT
> (for PHP 3)
        </P
><P
>&#13;         or <TT
CLASS="literal"
>AddType application/x-httpd-php .php</TT
> (for PHP 4)
        </P
><P
> 
         Also make sure that this AddType line is not hidden away inside a
          &#60;Virtualhost&#62; or &#60;Directory&#62; block which would
          prevent it from applying to the location of your test script.
        </P
></LI
><LI
><P
>&#13;         Finally, the default location of the Apache configuration files 
         changed between Apache 1.2 and Apache 1.3.  You should check to 
         make sure that the configuration file you are adding the AddType 
         line to is actually being read. You can put an obvious syntax error
         into your httpd.conf file or some other obvious change that will 
         tell you if the file is being read correctly.
        </P
></LI
></UL
>
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.activate-module"
></A
><B
>11. </B
>
      It says to use: <TT
CLASS="literal"
>--activate-module=src/modules/php4/libphp4.a</TT
>, 
      but  that file doesn't exist, so I changed it to 
      <TT
CLASS="literal"
>--activate-module=src/modules/php4/libmodphp4.a</TT
> and it 
      doesn't work!? What's going on?
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
       Note that the <TT
CLASS="filename"
>libphp4.a</TT
> file is not supposed to exist.  The
       apache process will create it!
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.ansi"
></A
><B
>12. </B
>
      When I try to build Apache with PHP as a static module using 
      <TT
CLASS="literal"
>--activate-module=src/modules/php4/libphp4.a</TT
> 
      it tells me that my compiler is not ANSI compliant.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      This is a misleading error message from Apache that has been fixed
      in more recent versions.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.apxs"
></A
><B
>13. </B
>
      When I try to build PHP using <TT
CLASS="literal"
>--with-apxs</TT
>
      I get strange error messages.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      There are three things to check here.  First, for some reason
      when Apache builds the apxs Perl script, it sometimes ends up
      getting built without the proper compiler and flags variables.
      Find your apxs script (try the command <B
CLASS="command"
>which apxs</B
>, 
      it's sometimes found in <TT
CLASS="filename"
>/usr/local/apache/bin/apxs</TT
>
      or <TT
CLASS="filename"
>/usr/sbin/apxs</TT
>.
      Open it and check for lines similar to these:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>my $CFG_CFLAGS_SHLIB  = ' ';          # substituted via Makefile.tmpl
my $CFG_LD_SHLIB      = ' ';          # substituted via Makefile.tmpl
my $CFG_LDFLAGS_SHLIB = ' ';          # substituted via Makefile.tmpl</PRE
></TD
></TR
></TABLE
>
      If this is what you see, you have found your problem.  They may 
      contain just spaces or other incorrect values, such as 'q()'.  Change 
      these lines to say:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>my $CFG_CFLAGS_SHLIB  = '-fpic -DSHARED_MODULE'; # substituted via Makefile.tmpl
my $CFG_LD_SHLIB      = 'gcc';                   # substituted via Makefile.tmpl
my $CFG_LDFLAGS_SHLIB = q(-shared);              # substituted via Makefile.tmpl</PRE
></TD
></TR
></TABLE
>
      The second possible problem should only be an issue on Red Hat 6.1
      and 6.2.  The apxs script Red Hat ships is broken.  Look for this line:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>my $CFG_LIBEXECDIR    = 'modules';         # substituted via APACI install</PRE
></TD
></TR
></TABLE
>
      If you see the above line, change it to this:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>my $CFG_LIBEXECDIR    = '/usr/lib/apache'; # substituted via APACI install</PRE
></TD
></TR
></TABLE
>
       Last, if you reconfigure/reinstall Apache, add a <B
CLASS="command"
>make clean</B
> 
       to the process after <B
CLASS="command"
>./configure</B
> and before <B
CLASS="command"
>make</B
>.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.microtime"
></A
><B
>14. </B
>
     During <B
CLASS="command"
>make</B
>, I get errors in microtime, and a lot of <TT
CLASS="literal"
>RUSAGE_</TT
> stuff.
    </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      During the <B
CLASS="command"
>make</B
> portion of installation, if you encounter problems 
      that look similar to this:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>microtime.c: In function `php_if_getrusage':
microtime.c:94: storage size of `usg' isn't known
microtime.c:97: `RUSAGE_SELF' undeclared (first use in this function)
microtime.c:97: (Each undeclared identifier is reported only once
microtime.c:97: for each function it appears in.)
microtime.c:103: `RUSAGE_CHILDREN' undeclared (first use in this function)
make[3]: *** [microtime.lo] Error 1
make[3]: Leaving directory `/home/master/php-4.0.1/ext/standard'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/master/php-4.0.1/ext/standard'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/master/php-4.0.1/ext'
make: *** [all-recursive] Error 1</PRE
></TD
></TR
></TABLE
>
     </P
><P
>&#13;     Your system is broken.  You need to fix your <TT
CLASS="filename"
>/usr/include</TT
> files by
     installing a glibc-devel package that matches your glibc.  This has
     absolutely nothing to do with PHP.  To prove this to yourself, try this
     simple test:
     <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>$ cat &#62;test.c &#60;&#60;X
#include &#60;sys/resource.h&#62;
X
$ gcc -E test.c &#62;/dev/null</PRE
></TD
></TR
></TABLE
>
      If that spews out errors, you know your include files are messed up. 
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.upgrade"
></A
><B
>15. </B
>
      I want to upgrade my PHP. Where can I find the <B
CLASS="command"
>./configure</B
>
      line that was used to build my current PHP installation?
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      Either you look at config.nice file, in the source tree of your current PHP
      installation or, if this is not available, you simply run a 
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>&#60;?php phpinfo(); ?&#62;</PRE
></TD
></TR
></TABLE
>
      script. On top of the output the <B
CLASS="command"
>./configure</B
> line, that was used
      to build this PHP installation is shown.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.build.gdlibs"
></A
><B
>16. </B
>
      When building PHP with the GD library it either gives strange compile errors
      or segfaults on execution.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      Make sure your GD library and PHP are linked against the same depending
      libraries (e.g. libpng).
     </P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="faq.installation.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="faq.using.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Installation</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="faq.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Using PHP</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>