From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Andreas Schwab <schwab@suse.de>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: make bootstrap in separate build directory will overwrite loaddefs.el
Date: Wed, 20 Feb 2002 08:44:33 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1020220084419.21448F-100000@is> (raw)
In-Reply-To: <x5k7t9r7b2.fsf@tupik.goethe.zz>
On 19 Feb 2002, David Kastrup wrote:
> Andreas Schwab <schwab@suse.de> writes:
>
> > David.Kastrup@t-online.de (David Kastrup) writes:
> >
> > |> Now the question is whether
> > |> make bootstrap
> > |> can get off the ground without requiring an initial loaddefs.el.
> >
> > You can't. Dumping Emacs requires loaddefs.el, but that can only be
> > generated if you have already built Emacs previously. Chicken'n'egg.
>
> Well, one could rename the CVS version of loaddefs.el to something
> like
> loaddefs-bootstrap.el
> and then the Makefile would copy to loaddefs.el prior to doing the
> bootstrap just in case the latter has not been generated yet.
>
> It simply makes CVS maintenance more of a hassle if CVS-controlled
> files get overwritten in the course of compilation.
>
> --
> David Kastrup, Kriemhildstr. 15, 44793 Bochum
> Email: David.Kastrup@t-online.de
>
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-20 6:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <x5g040j6is.fsf@tupik.goethe.zz>
2002-02-19 6:37 ` make bootstrap in separate build directory will overwrite loaddefs.el Richard Stallman
2002-02-19 7:48 ` David Kastrup
2002-02-19 9:42 ` Eli Zaretskii
2002-02-19 9:59 ` David Kastrup
2002-02-19 10:08 ` Per Abrahamsen
2002-02-19 11:57 ` Eli Zaretskii
2002-02-19 14:04 ` Per Abrahamsen
2002-02-19 11:58 ` Andreas Schwab
2002-02-19 12:21 ` David Kastrup
2002-02-19 12:54 ` Andreas Schwab
2002-02-20 6:44 ` Eli Zaretskii [this message]
2002-02-20 6:47 ` Eli Zaretskii
2002-02-19 14:03 ` Stefan Monnier
2002-02-20 22:12 ` Richard Stallman
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=Pine.SUN.3.91.1020220084419.21448F-100000@is \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=schwab@suse.de \
/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).