./configure step fails

Bug #438895 reported by dyna
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PHP-FPM
Invalid
Medium
Unassigned

Bug Description

I'm attempting to do the integrated install for PHP 5.3.0 with the 0.6 version of PHP-FPM. I've tried the direct download off main page, and grabbing the tar straight from Git.
However, once I hit the ./configure step, I just get a lot of errors, primarily of type:

 =====
../configure: line 17295: 5: Bad file descriptor
../configure: line 17296: 6: Bad file descriptor
../configure: line 17312: 5: Bad file descriptor
../configure: line 17313: 6: Bad file descriptor
../configure: line 17331: 5: Bad file descriptor
../configure: line 17332: 6: Bad file descriptor
=====
and
=====
../configure: line 100550: ac_fn_c_check_header_mongrel: command not found
../configure: line 100923: #define ZEND_MODULE_API_NO : command not found
=====

It may be relevant that on the ./buildconf --force step, I have the following warnings:
=====
./buildconf --force
Forcing buildconf
using default Zend directory
buildconf: checking installation...
buildconf: autoconf version 2.64 (ok)
buildconf: Your version of autoconf likely contains buggy cache code.
           Running cvsclean for you.
           To avoid this, install autoconf-2.13.
rebuilding configure
configure.in:501: warning: AC_CACHE_VAL(have_broken_glibc_fopen_append, ...): suspicious cache-id, must contain _cv_ to be cached
=====

Linux 2.6.30-ARCH #1 SMP PREEMPT i686 Pentium II (Klamath) GenuineIntel GNU/Linux

Revision history for this message
dreamcat4 (dreamcat4) wrote :

Hmm,
I've seen errors like this before when building php. If patching an autoconf dependency file (like configure.in, ac_include.m4).

If the 'make' step forces php buildconf a second time and ruins configure. A way to avoid such may be to touch the timestaps of all files equal. touch -r [file] [other files].

However it might be something else here. I can see you have autoconf 2.64. There was a php error recently, we found it in karmic (ubuntu). Launchpad bug #411890

Revision history for this message
dreamcat4 (dreamcat4) wrote :

Otherwise if it was a timestamps mismatch:

When patching files like configure.in, aclocal.m4, configure can run twice. Later the compilation finishes with an error. If this happens use the debugging mode of the make command:

# `$(MAKE) --debug` instead of just `$(MAKE)` in the build stage.

Timestamps on the affected files can be fixed-up after patching (as quilt doesn't do it). For example to set the timestamps of (files...) equal to the "configure" timestamp:

# cd src-dir && touch -r configure files...

Revision history for this message
dyna (sbobkin) wrote :

It looks like it was as a result of PHP and the specific autoconf version, they insist on 2.13.
I used this patch to get around the problem: http://cvs.pld-linux.org/cgi-bin/cvsweb/packages/php/php-m4-divert.patch?rev=1.1
May as well close the bug here, as it's PHP/autoconf and not php-fpm.

dreamcat4 (dreamcat4)
Changed in php-fpm:
importance: Undecided → Medium
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.