downloads | documentation | faq | getting help | mailing lists | licenses | wiki | reporting bugs | sites | links | conferences | my

search for in the

What is SVN?

You can find more information about SVN, and download clients for most major platforms, at the official SVN site.


If you would like to join PHP development or would like to contribute to the PHP documentation, contact the relevant group. You will need your own SVN account to contribute.

Source and binary snapshots

You may also be interested in a PHP snapshot, see Compiled snapshots for Windows users are also included.

SVN Access

If you wish to get the latest PHP source tree, you can obtain it through SVN. You should be warned that the SVN version is a development version, and as such, is often unstable, and may not even compile properly. The advantage of using SVN, though, is that you can get the latest fixes and updates, without having to wait for the official releases.

PHP uses an advanced configuration system that requires you to have the following tools. re2c is only necessary for developers and can be found here. All other utilities can be obtained from the GNU FTP site.

If you're experiencing problems, see also the section on buildconf failures.

Steps for using PHP from SVN

Note to developers: SSL is set up, so use your credentials and to access SVN.

  1. The recommended way is to make a sparse checkout of the php-src directory only, then grab the parts that you need. This enables a single commit to span multiple branches.

    svn checkout --depth immediates php-src
    cd php-src
    svn update branches tags --set-depth immediates
    svn update trunk branches/PHP_5_4 branches/PHP_5_3 --set-depth infinity

    Or alternatively, you can fetch the current PHP source code and the active branches:

    PHP 5.3: svn checkout php-src-5.3
    PHP 5.4: svn checkout php-src-5.4
    PHP HEAD: svn checkout php-src-trunk

    The branch names can also be used for SVN diff and merge operations.
  2. Note that certain combinations of autoconf, automake and libtool may not work when used together. See below for details.
    Also, certain versions of autoconf may generate warnings of AC_PROG_CPP called before AC_PROG_CC. These messages can usually be ignored.

  3. Run ./buildconf to generate the configure script. This may take several moments.
  4. From this point onwards, installation is similar to the installation of one of the official packages with one main difference – you may need bison 1.28 or later and flex 2.5.4 (PHP 5.2 and earlier) or re2c 0.13.4+ or later (PHP 5.3 and later) to compile, because the pre-generated scanner and parser files may not be included in SVN.

There are many other things, such as the XML source code for the documentation, available via SVN. See the web-based view of the SVN server to see what is available. For example, to checkout the latest english version of the PHP manual:
svn checkout ./phpdoc-en

You can also check the SVN FAQ on the wiki.

autoconf, automake and libtool information

There seem to be problems with libtool 1.4.2. It is suggested that you use libtool 1.4, along with autoconf 2.13 and automake 1.4. You should also ensure that autoconf, automake and libtool are installed in the same directory. libtool 1.5 will not work.

The following combinations are known to work with PHP 5.3 and below:

If you have multiple versions of autoconf installed on your computer, as is common for many UNIXes, you can set the PHP_AUTOCONF and PHP_AUTOHEADER variables when running buildconf to indicate which versions it should use e.g.:
PHP_AUTOCONF=autoconf213 PHP_AUTOHEADER=autoheader213 ./buildconf

Zend/zend_language_scanner.c: No such file or directory

PHP only supports flex 2.5.4, not later versions as they broke backwards compatibility. Please note that PHP 5.3 and later do not require flex at all.

show source | credits | sitemap | contact | advertising | mirror sites