From: Eli Zaretskii <eliz@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: acm@muc.de, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Patch to INSTALL.CVS to clarify why `make bootstrap' sometimes fails.
Date: Sun, 08 Jun 2008 00:14:26 +0300 [thread overview]
Message-ID: <u7id1lzgt.fsf@gnu.org> (raw)
In-Reply-To: <85tzg5c6hu.fsf@lola.goethe.zz>
> From: David Kastrup <dak@gnu.org>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, acm@muc.de, emacs-devel@gnu.org
> Date: Sat, 07 Jun 2008 22:52:45 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Stefan Monnier <monnier@iro.umontreal.ca>
> >> Date: Sat, 07 Jun 2008 14:40:11 -0400
> >> Cc: emacs-devel@gnu.org
> >>
> >> `make bootstrap' should begin by doing a `maintainer-clean'.
> >
> > And then what does one do if a bootstrap fails half-way through, and
> > one wants to continue it after fixing the problem?
>
> That's an expert operation with tripup potential.
No, it isn't. Continuing from where the previous run with the same
arguments left off is a normal Make operation.
next prev parent reply other threads:[~2008-06-07 21:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 10:14 Patch to INSTALL.CVS to clarify why `make bootstrap' sometimes fails Alan Mackenzie
2008-06-07 11:58 ` Eli Zaretskii
2008-06-07 18:40 ` Stefan Monnier
2008-06-07 19:09 ` Miles Bader
2008-06-07 20:17 ` Stefan Monnier
2008-06-07 19:57 ` Glenn Morris
2008-06-07 20:20 ` Eli Zaretskii
2008-06-07 20:52 ` David Kastrup
2008-06-07 21:14 ` Eli Zaretskii [this message]
2008-06-07 22:22 ` David Kastrup
2008-06-08 6:42 ` Eli Zaretskii
2008-06-08 8:33 ` David Kastrup
2008-06-08 9:00 ` Eli Zaretskii
2008-06-08 9:32 ` David Kastrup
2008-06-08 19:01 ` Glenn Morris
2008-06-08 2:46 ` Eric Hanchrow
2008-06-08 3:28 ` Stefan Monnier
2008-06-08 5:38 ` Stephen J. Turnbull
2008-06-08 8:21 ` Richard M Stallman
2008-06-08 3:03 ` Stefan Monnier
2008-06-08 8:05 ` Alan Mackenzie
2008-06-09 1:08 ` Stefan Monnier
2008-06-07 19:55 ` Glenn Morris
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=u7id1lzgt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.