all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Wolfgang Jenkner <wjenkner@inode.at>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
	"Herbert J. Skuhra" <hskuhra@eumx.net>,
	emacs-devel@gnu.org
Subject: Re: Trunk: Build error on FreeBSD
Date: Tue, 18 Sep 2012 16:04:08 +0200	[thread overview]
Message-ID: <85ehlzxuxm.fsf@iznogoud.viz> (raw)
In-Reply-To: m21ui01dap.fsf@igel.home

On Tue, Sep 18 2012, Andreas Schwab wrote:

> It still does not exist.

Rev. 110082 reintroduces the original bug, which was at the beginning of
this story, viz.

$ ./autogen.sh && ./configure MAKE=gmake && gmake bootstrap

runs this line in config.status

${MAKE-make} MAKEFILE_NAME=do-not-make-Makefile epaths-force

with make instead of gmake.  This prevented src/epaths.h from being
generated because gmake was passing down indigestible MAKEFLAGS to an
unsuspecting make.

This time, this doesn't happen (with the default settings), but I'd like
to propose the following patch anyway.

Wolfgang

2012-09-18  Wolfgang Jenkner  <wjenkner@inode.at>

	* Makefile.in (bootstrap): Simplify last change.

=== modified file 'Makefile.in'
--- Makefile.in	2012-09-17 22:43:12 +0000
+++ Makefile.in	2012-09-18 12:57:30 +0000
@@ -894,13 +894,8 @@
 #  * Build Makefile, to build the build procedure itself.
 #  * Do the actual build.
 bootstrap: bootstrap-clean FRC
-	cd $(srcdir) && { ./autogen.sh || autogen/copy_autogen; }
-	if [ -x config.status ]; then \
-	    ./config.status --recheck && \
-	    ./config.status; \
-	else \
-	    $(srcdir)/configure $(CONFIGURE_FLAGS); \
-	fi
+	cd $(srcdir) && { ./autogen.sh || autogen/copy_autogen; } && touch configure
+	$(MAKE) $(MFLAGS) Makefile
 	$(MAKE) $(MFLAGS) info all
 
 .PHONY: check-declare




  parent reply	other threads:[~2012-09-18 14:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-15  8:44 Trunk: Build error on FreeBSD Herbert J. Skuhra
2012-09-15  9:33 ` Paul Eggert
2012-09-15 12:48   ` Wolfgang Jenkner
2012-09-17 13:04     ` Wolfgang Jenkner
2012-09-17 21:52       ` Paul Eggert
2012-09-17 22:12         ` Andreas Schwab
2012-09-17 22:37           ` Paul Eggert
2012-09-17 22:42             ` Andreas Schwab
2012-09-17 23:11               ` Paul Eggert
2012-09-18 14:04               ` Wolfgang Jenkner [this message]
2012-09-22  7:40                 ` Paul Eggert
2012-09-22 10:25                   ` Wolfgang Jenkner
2012-09-22 11:04                     ` Paul Eggert
2012-09-22 11:17                       ` Wolfgang Jenkner
2012-09-22 14:32                         ` Wolfgang Jenkner
2012-09-22 19:00                           ` Paul Eggert
2012-09-23 11:42                             ` Wolfgang Jenkner
2012-09-23 16:02                               ` Paul Eggert
2012-09-23 20:09                                 ` Wolfgang Jenkner
2012-09-17 22:42         ` Herbert J. Skuhra
2012-09-17 23:23           ` Herbert J. Skuhra
2012-09-18  2:51         ` Stefan Monnier
2012-09-15 20:57   ` Herbert J. Skuhra
2012-09-16  3:42     ` Paul Eggert
2012-09-16 14:39       ` Herbert J. Skuhra
2012-09-16 16:40         ` Paul Eggert
2012-09-17 11:44           ` Herbert J. Skuhra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85ehlzxuxm.fsf@iznogoud.viz \
    --to=wjenkner@inode.at \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=hskuhra@eumx.net \
    --cc=schwab@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.