Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3CE9300B.2030804@ece.gatech.edu>
Date: Mon, 20 May 2002 13:19:07 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: autoconf-devel-2.53a-1
References: <20020519224501 DOT E4EF91B854 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Charles Wilson wrote:


> o There DOES seem to a problem in BOTH 2.53 and 2.53a, where
>    seemingly valid configure.in/acinclude.m4 files lead to buggy
>    configure scripts.  This bug ALSO exists in 2.52.  So, in that
>    respect, 2.53a-1 is no worse than any other cygwin release
>    of autoconf-devel.

According to Akim (chief autoconf guru on the autoconf mailing list), 
the problem IS in my configure.in/acinclude.m4 files.  We haven't yet 
nailed down exactly WHERE the problem is -- but he says it's NOT in 
autoconf itself.

So, sorry for the false alarm...

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/