From: Paul Eggert <eggert@cs.ucla.edu>
To: Andreas Schwab <schwab@linux-m68k.org>,
"Herbert J. Skuhra" <hskuhra@eumx.net>,
emacs-devel@gnu.org
Subject: Re: Trunk: Build error on FreeBSD
Date: Sat, 22 Sep 2012 04:04:45 -0700 [thread overview]
Message-ID: <505D9B4D.3050407@cs.ucla.edu> (raw)
In-Reply-To: <85r4pu73s6.fsf@iznogoud.viz>
>> "bootstrap-clean" removes Makefile,
> It doesn't.
Right you are. Sorry about that.
>> I don't see why the "touch configure" is needed.
>
> Probably, because no configure was generated (as Andreas remarked).
Andreas was fairly cryptic, but what I *think* he was saying
was the Makefile should use $(srcdir)/configure, not ./configure,
since ./configure does not exist when we're doing an out-of-tree build.
If I understood him correctly, there should be no need to touch
$(srcdir)/configure. If I'm wrong I hope somebody corrects me.
Thanks again for following up. I installed the following
as trunk bzr 110134.
=== modified file 'ChangeLog'
--- ChangeLog 2012-09-22 09:46:20 +0000
+++ ChangeLog 2012-09-22 10:59:13 +0000
@@ -1,5 +1,9 @@
2012-09-22 Paul Eggert <eggert@cs.ucla.edu>
+ * Makefile.in (bootstrap): Simplify build procedure.
+ Suggested by Wolfgang Jenker in
+ <http://lists.gnu.org/archive/html/emacs-devel/2012-09/msg00456.html>.
+
Merge from gnulib, incorporating:
2012-09-22 sockets, sys_stat: remove AC_C_INLINE in MSVC-only cases
=== modified file 'Makefile.in'
--- Makefile.in 2012-09-17 22:43:12 +0000
+++ Makefile.in 2012-09-22 10:59:13 +0000
@@ -889,18 +889,13 @@
.PHONY: bootstrap
# Bootstrapping does the following:
-# * Remove files to start from a clean slate.
+# * Remove files to start from a bootstrap-clean slate.
# * Run autogen.sh, falling back on copy_autogen if autogen.sh fails.
-# * Build Makefile, to build the build procedure itself.
+# * Rebuild Makefile, to update 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
+ $(MAKE) $(MFLAGS) Makefile
$(MAKE) $(MFLAGS) info all
.PHONY: check-declare
next prev parent reply other threads:[~2012-09-22 11: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
2012-09-22 7:40 ` Paul Eggert
2012-09-22 10:25 ` Wolfgang Jenkner
2012-09-22 11:04 ` Paul Eggert [this message]
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=505D9B4D.3050407@cs.ucla.edu \
--to=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.