Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 22 Sep 2002 11:13:32 -0700 From: Bruce Alderson Subject: Re: Trouble w/ autoheader -> autom4te error In-reply-to: To: cygwin AT cygwin DOT com Message-id: <1032718412.2106.6.camel@h24-69-127-23> MIME-version: 1.0 Content-type: multipart/signed; boundary="=-b/f6a9cflkNxDiKoqXsh"; protocol="application/pgp-signature"; micalg=pgp-sha1 References: <20020922165459 DOT 75618 DOT qmail AT web21009 DOT mail DOT yahoo DOT com> --=-b/f6a9cflkNxDiKoqXsh Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > I was told over at the autoconf List that I should be using 2.54 because > 2.53 'is an early alpha release'. I wonder if there are users on List > here who might have been using a Autoconf-2.54 they've built themselves > from GNU mainline source?=20 We're still using 2.53a (or b?), as something in 2.54 seems to break one of our m4 scripts on Win32. =20 I didn't have time to look into the problem, though. The report came from an off-site developer who had installed autoconf 2.54 by-hand ... and I suspect he may have missed a related versions of one of the other Gnu auto tools (I assume they are somewhat interdependent). -mx --=-b/f6a9cflkNxDiKoqXsh Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9jghMGq1MJ2W/DBURAsawAKCOyfx95CDIO9d6j5ok8WXj/z0NxQCeOzmK ImPmFXzosZ8yiEgI21MdeXU= =xUZC -----END PGP SIGNATURE----- --=-b/f6a9cflkNxDiKoqXsh--