From: Richard Stallman <rms@gnu.org>
Cc: storm@cua.dk, schwab@suse.de, tra@biobase.dk, emacs-devel@gnu.org
Subject: Re: Emacs in CVS as today does not build - emacs depends on *.elc, which cannot be built without emacs
Date: Sat, 23 Nov 2002 17:57:25 -0500 [thread overview]
Message-ID: <E18FjDJ-00038W-00@fencepost.gnu.org> (raw)
In-Reply-To: <85lm3mg8f1.fsf@newton.ch.collab.net> (message from Karl Fogel on 21 Nov 2002 11:05:38 -0600)
The method you described wasn't completely fleshed out, and left a few
practical issues unaddressed. Nevertheless, my original patch
implemented it, or something very close to it,
It was not close at all. Your first script actually ran the bootstrap
procedure. That is very different from what I suggested.
However, if we can come up with some precise description of how
autogen.sh should behave, I'd be happy to implement it.
Here's the description I wrote before:
I think it should create a file `must-bootstrap'. Then
the next `make all' run should notice the existence of must-bootstrap,
and do a bootstrap automatically.
Could you be more specific about why you think that is hard?
It could be implemented inside the rule maybe-bootstrap.
next prev parent reply other threads:[~2002-11-23 22:57 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 21:42 Emacs in CVS as today does not build - emacs depends on *.elc, which cannot be built without emacs Thorbjørn Ravn Andersen
2002-10-29 21:55 ` Thorbjørn Ravn Andersen
2002-10-30 22:00 ` Kim F. Storm
2002-10-31 8:10 ` Thorbjørn Ravn Andersen
2002-10-31 14:14 ` Eli Zaretskii
2002-10-31 14:40 ` Thorbjørn Ravn Andersen
2002-10-31 14:55 ` Andreas Schwab
2002-10-31 16:24 ` Thorbjørn Ravn Andersen
2002-10-31 17:01 ` Stefan Monnier
2002-11-01 0:41 ` Steven Tamm
2002-11-01 15:34 ` Stefan Monnier
2002-11-02 17:15 ` Andreas Schwab
2002-11-03 2:24 ` Stefan Monnier
2002-11-03 23:27 ` Juanma Barranquero
2002-11-04 7:20 ` Kai Großjohann
2002-11-04 14:53 ` Stefan Monnier
2002-11-04 15:24 ` Andreas Schwab
2002-11-04 15:26 ` Stefan Monnier
2002-11-04 15:31 ` Juanma Barranquero
2002-11-04 15:43 ` Stefan Monnier
2002-11-04 16:17 ` Juanma Barranquero
2002-11-02 3:32 ` Richard Stallman
2002-11-01 8:34 ` Thorbjørn Ravn Andersen
2002-11-01 15:40 ` Stefan Monnier
2002-11-03 8:13 ` Thorbjørn Ravn Andersen
2002-11-03 8:36 ` Alfred M. Szmidt
2002-11-03 9:10 ` Thorbjørn Ravn Andersen
2002-11-04 12:02 ` Richard Stallman
2002-10-31 18:10 ` Andreas Schwab
2002-11-02 3:32 ` Richard Stallman
2002-11-02 2:37 ` Karl Fogel
2002-11-03 13:56 ` Richard Stallman
2002-11-04 1:31 ` Karl Fogel
2002-11-04 18:06 ` Richard Stallman
2002-11-20 1:42 ` Karl Fogel
2002-11-20 11:29 ` Kim F. Storm
2002-11-20 17:05 ` Karl Fogel
2002-11-21 17:13 ` Richard Stallman
2002-11-21 17:05 ` Karl Fogel
2002-11-23 22:57 ` Richard Stallman [this message]
2002-11-21 17:12 ` Richard Stallman
2002-11-01 9:39 ` Richard Stallman
2002-10-31 19:03 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E18FjDJ-00038W-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
--cc=storm@cua.dk \
--cc=tra@biobase.dk \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).