Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32026
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain daleenterprise.com from 67.78.11.229 cause and error)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <46DC5EB6.8020805@mysql.com>
References: <20CECB37-7174-498C-85EA-A862923E594D@daleenterprise.com> <1188809931.3317.0.camel@localhost.localdomain> <C0C21D32-D496-49E1-92E0-A860E866CAF4@daleenterprise.com> <46DC0FFC.9040403@mysql.com> <4AA18585-8F96-4A6E-A990-E5FAD0DECA7E@daleenterprise.com> <46DC5EB6.8020805@mysql.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <68CEA915-CA7B-495B-B9D1-0B29A01EDAE3@daleenterprise.com>
Content-Transfer-Encoding: 7bit
Date: Mon, 3 Sep 2007 15:51:11 -0400
To: PHP Developers Mailing List <internals@lists.php.net>
MTA-Interface: amavisd-new-2.3.3 (2005-08-22) + Maia Mailguard 1.1.0 at daleenterprise.com
Subject: Re: [PHP-DEV] buildconf and the generated configure script for PHP6 is faulty.
From: buildsmart@daleenterprise.com (BuildSmart)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Sep 3, 2007, at 15:21:26, Hartmut Holzgraefe wrote:

> Dear Mr. BuildSmart
>
>> I didn't change my autoconf to correct the problem, that is an  
>> assumption on your part,
>
> talking about assumptions: i didn't claim that changing the
> autoconf version used was what you did but what you should
> have done ...

Well perhaps you have a bad memory because you stated the autoconf  
2.13 generated version works and I don't have 2.13 installed and a  
configure script isn't provided so you must have assumed I generated  
the working one with 2.13 otherwise you would not have mentioned  
anything about autoconf 2.13 generating a working configure script.

>
>> I edited 2 lines in a m4 file supplied in the  PHP6 distro.
>
> Oh? That may be what you did (in which case it would be
> interesting to know *which* m4 file and how the actual
> change looks like), what you *sent* though was a change
> to the generated configure file, not to any of the
> *.m4 files it was created from ...

I sent no changed file, I provided a link to the faulty (un-edited)  
configure script, I explained that two lines were ending up in the  
wrong place, I showed where they are, and where they should be.

Since you believe it's an autoconf bug and don't support any other  
version of autoconf there is no need to pursue the matter further,  
I've noted the issue internally as an unsupported autoconf version fix.

>
> -- 
> Hartmut Holzgraefe, Principal Support Engineer

- --Dale


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)

iD8DBQFG3GWv0hzWbkf0eKgRAv7HAJ9yTxlUTBE91No+HZfbSGbT6wvMlQCfWtEX
IIgVUnY6PpI84L5TggxuSlA=
=JUqW
-----END PGP SIGNATURE-----