Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25976
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.169 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:date:from:reply-to:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=Uli/pQ8GRlu+GCDpYoNngpYdwbpzCz9/4fIDlZxoXIN2l76M+hoWRjduDQaxi2MUKaZD7km2G3rlBWXlz5O5z+Eb1znHARLBG4ApMt+b+bAZrseKSVnMS+7tSVlsbYNy2UeH5mAclRlARInNs6LEX9DFY8039bDGWWgEfrDI3Y0=
Date: Fri, 06 Oct 2006 10:35:57 -0700
Reply-To: OpenMacNews <openmacnews@gmail.com>
To: Ilia Alshanetsky <ilia@prohost.org>
cc: php internals LIST <internals@lists.php.net>
Message-ID: <47246C6F990B6361212CD7AF@[172.30.11.6]>
In-Reply-To: <132A9C4E-1B31-4CD9-B0C8-587874861B6D@prohost.org>
References: <5E7827565D45A420B4C648BE@[172.30.11.6]>
 <132A9C4E-1B31-4CD9-B0C8-587874861B6D@prohost.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [PHP-DEV] why does php support 'only' out-of-date/obsolete
 versions of automake/autoconf?
From: openmacnews@gmail.com (OpenMacNews)

hi ilia,

> PHP works just fine with newer version of autoconf and automake.  For
> example I am using autoconf 2.60 and automake 1.9.6 and not
> experiencing any build issues. One of the reasons we recommend
> autoconf 2.13 is because it has a non-broken implementation of config
> test caching and unlike autoconf 2.60 does not require re-running of
> every configuration test on PHP rebuild.

yes, i know it "works" fine :-)  in fact, i personally build/use php 
52cvs with:

	autoconf (GNU Autoconf) 2.60
	automake (GNU automake) 1.9.6

on my osx 10.4.8 box.

the problem is that *other* php-related projects' code breaks with 
recent versions of automake.

of course, i 1st tried to talk to the project's developer about the 
issue.

the response was, roughly, that -- since php "only supports automake 
1.4" that they'll only support v1.4.

which is all fine & good -- except when the developer of the 'other' 
project is also ON the php-development team as well.

in response to questions abt this @ #php, one dev's response -- 
probably very accurate -- is that this is the case because "autoconf 
issues are boring to work on".

one great big catch-22 :-(