From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Moreton Newsgroups: gmane.emacs.devel Subject: Re: Bootstrap failure on MS-Windows Date: Fri, 08 Nov 2013 10:32:02 +0000 Message-ID: References: <134n7uab5v.fsf@fencepost.gnu.org> <83r4au7li4.fsf@gnu.org> <83mwli7gwq.fsf@gnu.org> <837gcl7917.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1383906748 1226 80.91.229.3 (8 Nov 2013 10:32:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 8 Nov 2013 10:32:28 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 08 11:32:33 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VejMd-0000FS-VH for ged-emacs-devel@m.gmane.org; Fri, 08 Nov 2013 11:32:32 +0100 Original-Received: from localhost ([::1]:44790 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VejMd-0006Xj-Gs for ged-emacs-devel@m.gmane.org; Fri, 08 Nov 2013 05:32:31 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43465) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VejMU-0006PV-Jw for emacs-devel@gnu.org; Fri, 08 Nov 2013 05:32:28 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VejMO-0004At-RS for emacs-devel@gnu.org; Fri, 08 Nov 2013 05:32:22 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:33071) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VejMO-0004Af-Kr for emacs-devel@gnu.org; Fri, 08 Nov 2013 05:32:16 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VejML-0007pG-LJ for emacs-devel@gnu.org; Fri, 08 Nov 2013 11:32:13 +0100 Original-Received: from uk.solarflare.com ([193.34.186.16]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 08 Nov 2013 11:32:13 +0100 Original-Received: from andrewjmoreton by uk.solarflare.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 08 Nov 2013 11:32:13 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 59 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: uk.solarflare.com User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (windows-nt) Cancel-Lock: sha1:kaFOUhHa71N9CKqKEWtjhhlzcNY= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:165068 Archived-At: On Wed 06 Nov 2013, Andy Moreton wrote: > On Wed 06 Nov 2013, Eli Zaretskii wrote: > >>> From: Andy Moreton >>> Date: Wed, 06 Nov 2013 13:59:26 +0000 >>> >>> When "make bootstrap" reruns configure, it produces different output >>> to configure run on its own, and it looks like it is ignoring the >>> site config that msysconfig provides. >> >> Not here. If it does that on your system, that's some bug that needs >> to be investigated. > > Thanks for the hint Eli - you are right as usual. > > After further investigation this turned out to be a problem in my > wrapper script which was passing configure args in the environment > rather than on the configure command line. After more testing, it turns out this is not the case. The scenario that goes wrong is: 1) Begin with a clean bzr checkout 2) Run 'autogen.sh" and 'nt/msysconfig.sh' and 'make' as usual 3) Time passes, and configure.ac is updated after a bzr pull 4) Run 'make bootstrap', and observe that the CONFIG_SITE file is not used when configure is run from the make, leading to incorrect configure results and a failed bootstrap. --[make bootstrap]-------------------------------------------- rm -f config.cache config.log cd .. && ./autogen.sh Checking whether you have the necessary tools... (Read INSTALL.BZR for more details on building Emacs) Checking for autoconf (need at least version 2.65)... ok Checking for automake (need at least version 1.11)... ok Your system has the required tools, running autoreconf... You can now run `./configure'. /usr/bin/make MAKEFILE_NAME=force-Makefile force-Makefile make[1]: Entering directory `/c/emacs/src/emacs/trunk/obj-mingw32' if [ -x ./config.status ]; then \ ./config.status --recheck; \ else \ ../configure --cache-file=/dev/null; \ fi running CONFIG_SHELL=/bin/sh /bin/sh ../configure --prefix=C:/emacs-trunk --with-pkg-config-prog=C:/emacs/mingw-devel/bin/pkg-config --enable-checking --without-rsvg CPPFLAGS= -IC:/emacs/mingw-devel/include -IC:/emacs/mingw-devel/src/xpm/3.5.1/libXpm-3.5.1-src/lib LDFLAGS= -LC:/emacs/mingw-devel/lib --no-create --no-recursion checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes --[make bootstrap]-------------------------------------------- The easiest way to notice the incorrect configure results is to look for the ACL tests. In a good msys configure, this comes from the site file, whereas in the failed case it runs the autoconf tests. AndyM