- Always use the shtool mkdir.

Allow shared modules to be built using $(CXX)

fix quotes

Always use the libtool which is build in the top_builddir.

- Updated libtool to 1.4.3 which has test for the sed problem..

relabel

Provide alternative for glibc brokenness test when cross compiling

Raise required OpenSSL version to 0.9.6.

Workaround for glibc 2.2.9x and later "a+" bug that does not seek to EOF for
files fopen()ed with that mode.

Merge streams changes from branch.

use grep -E instead of egrep. the latter is not defined by POSIX anymore

- Remove PHP_DISABLE_CLI
- Streamline ircg build: thttpd-dependent part moved into separate source
file, so that it can be added to the SAPI-only object list.

- Remove the "which" call and just expect sed to be in PATH

- Only test the sed in PATH. (testing others is useless)

Make PHP compile out-of-the-box with uClibc

Quote macro names in AC_DEFUN() and prefix the internal macros using
a single underscore. Also rename AC_PHP_ONCE as PHP_RUN_ONCE.

remove the remains of that comment.

- Moved CGI specific lines from configure.in to sapi/cgi/config9.m4
which is 'executed' last of the SAPI config.m4's.
- Added --disable-cgi option. (was possible only with above change)

- Moved CGI specific lines from configure.in to sapi/cgi/config9.m4
which is 'executed' last of the SAPI config.m4's.
- Added --disable-cgi option. (was possible only with above change)
- Made the sed check to not test for the possibly working sed on Solaris
since that would make the test quite useless. (compile would still fail)

# That sed check is not enabled yet..need to know whether we fail
# during configure or just put out a warning about possible non-working
# sed. As even plain ./configure doesn't work in most cases, I think
# it would be better to just fail during configure and let the users
# fix their paths/install GNU sed.

show more ...

- Fix typo..
#
# Note: This is not used at all yet..waiting for comments first. :)
#

- Added PHP_PROG_SED which checks whether the sed in system works with
very long strings.

#
# Sascha, is this okay? I added this here since any libtool/autoconf
# release out t

- Added PHP_PROG_SED which checks whether the sed in system works with
very long strings.

#
# Sascha, is this okay? I added this here since any libtool/autoconf
# release out there doesn't have this yet..we can remove this when
# we can really start requiring such versions which have it?
#
# This sets $SED to the correct binary, so that should be used in
# places were the lines might be very long.
#

show more ...

Check for C99 conformance of snprintf.
#This way we force using internal version if a broken library is used.
#E.g. length parameter is broken, return value or default precision wrong.

Another Linux x86 system returns ELIMIT so we need to check errno as well
before assuming that pread/pwrite work.

The pread/pwrite macros check for a bug in the Linux glibc now.
The bug causes the kernel not to return -1/EAGAIN. The new test case
has been borrowed from the Linux Test Project.

Th

The pread/pwrite macros check for a bug in the Linux glibc now.
The bug causes the kernel not to return -1/EAGAIN. The new test case
has been borrowed from the Linux Test Project.

This also fixes a bug which apparently caused HAVE_PREAD/WRITE to be
defined even if the more complex checks failed (ac_cv_func_NAME=no
was set albeit with no difference).

show more ...

remove unused lines

Follow Yasuo's suggestion and build sapi program's under the sapi-specific
directory.

Move sapi-specific makefile fragments to their respective directory.

Create an embed sapi m

Follow Yasuo's suggestion and build sapi program's under the sapi-specific
directory.

Move sapi-specific makefile fragments to their respective directory.

Create an embed sapi module which resides in its own dir now.

show more ...