X-Spam-Check-By: sourceware.org Message-ID: <45A0B56F.9010900@users.sourceforge.net> Date: Sun, 07 Jan 2007 02:55:11 -0600 From: "Yaakov (Cygwin Ports)" User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [patch] cygport-0.2.7 autoconf-2.61/automake-1.10 support References: <459F0711 DOT 5080705 AT cwilson DOT fastmail DOT fm> In-Reply-To: <459F0711.5080705@cwilson.fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Charles Wilson wrote: > * bin/cygport.in: use --datarootdir in preference > to --datadir/--infodir/--mandir when using > autoconf-2.60 and later. Thanks. Fixed in CVS. > * autogen.sh: Ensure that autoconf will not complain > when it is newer than the one previously used (needed > because automake-1.10's aclocal now inserts more stringent > checking into aclocal.m4) Investigating further, I got this error while running autogen.sh in the CVS tree but not with autoreconf in the -src tarball. The former after 'aclocal --force' still showed dep on ac-2.60, where the latter showed ac-2.61. I finally figured out that the difference was caused solely by autom4te.cache; removing that allowed autogen.sh to proceed. Therefore I have added a 'rm -fr autom4te.cache' to autogen.sh in CVS, and no more. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFoLVvpiWmPGlmQSMRCP/JAJ9WWw/rVT+vaul9x6I+iW+nkBSgwwCfSO/v puSpuYw/9G54ABMgw730KNc= =Bd2+ -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/