From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1JLkcD-000736-OQ for mharc-grub-devel@gnu.org; Sun, 03 Feb 2008 14:34:57 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JLkcC-000731-Sh for grub-devel@gnu.org; Sun, 03 Feb 2008 14:34:56 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JLkcA-00072j-Go for grub-devel@gnu.org; Sun, 03 Feb 2008 14:34:55 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JLkcA-00072e-9Z for grub-devel@gnu.org; Sun, 03 Feb 2008 14:34:54 -0500 Received: from c60.cesmail.net ([216.154.195.49]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.60) (envelope-from ) id 1JLkcA-0000Wg-2e for grub-devel@gnu.org; Sun, 03 Feb 2008 14:34:54 -0500 Received: from unknown (HELO relay.cesmail.net) ([192.168.1.81]) by c60.cesmail.net with ESMTP; 03 Feb 2008 14:34:52 -0500 Received: from [192.168.1.28] (pool-96-227-20-21.phlapa.east.verizon.net [96.227.20.21]) by relay.cesmail.net (Postfix) with ESMTP id 51BE2619055 for ; Sun, 3 Feb 2008 14:34:52 -0500 (EST) From: Pavel Roskin To: The development of GRUB 2 Content-Type: text/plain Date: Sun, 03 Feb 2008 14:34:51 -0500 Message-Id: <1202067291.21357.11.camel@rd> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-1.fc8) Content-Transfer-Encoding: 7bit X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. Subject: Requiring Autoconf 2.61 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2008 19:34:57 -0000 Hello! I suggest that we require Autoconf 2.61 in configure.ac. It has been out for over a year. It's easy to install locally without breaking anything. It generates more portable configure scripts than older version of Autoconf (at least it's supposed to, unless there are regressions). I see that configure scripts generated by Autoconf 2.59 and 2.61 are committed to the GRUB CVS alternately. If the current configure is made by Autoconf 2.59, and it's regenerated on my system by Autoconf 2.61, I see unnecessary differences. If somebody has an older version of Autoconf and doesn't want to upgrade, there is always an option to run "touch configure" to provent make from trying to regenerate it. In addition to configure, there are also subtle differences in config.h.in, which is generated by autoheader. -- Regards, Pavel Roskin