From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: Stefan Monnier <monnier+gnu/emacs@rum.cs.yale.edu>, emacs-devel@gnu.org
Subject: bootstrap (was: Emacs-diffs digest, Vol 1 #508 - 12 msgs)
Date: Tue, 26 Mar 2002 10:31:27 -0500 [thread overview]
Message-ID: <200203261531.g2QFVRR17627@rum.cs.yale.edu> (raw)
In-Reply-To: Pine.SUN.3.91.1020326075527.23050D-100000@is
> I think we should do something to avoid the warning in the bootstrap
> case, then. Users who don't know these details might become spooked by
> the warning, especially if they were used to get a fatal error with the
> same language before.
An alternative is to just do
(if ...bootstrapping...
(setq purify-flag nil))
at the beginning of loadup.el.
> > PS: I almost got bootstrapping to work without a `bootstrap-emacs'
> > executable (by byte-compiling with `temacs' instead)
> > but hit a problem where `temacs -batch' freezes in call-process:
> > the problem is that the SIGCHLD handler is not installed in that
> > case (probably because it might introduce problems when we dump).
>
> Yes, I think that's the reason why signals aren't caught.
>
> > As for why `call-process' is called: vc.el does
> > (eval-when-compile (require 'ediff-util)) and ediff-util.el
> > ends up loading all the ediff*.el files (also from within
> > `eval-when-compile' clauses) and ediff-ptch.el runs patch with a few
> > different args to determine the default value of a config variable.
>
> We could prevent this by binding some special variables during bootstrap, no?
As I said I'd rather have less bootstrap-specific code than more, so it
doesn't sound like an attractive solution. Other solutions are:
- create `eval-only-when-compile' since the (require 'ediff-util) is only
done to get rid of some compiler warnings (it doesn't provide any
macros used by vc.el as far as I can tell).
- check !noninteractive||initialized in call-process and return nil
without running any program otherwise (since the SIGCHLD handler
is not installed).
- check !noninteractive||initialized in call-process and install
the SIGCHLD handler if the check fails.
Obviously the first solution is the only one that's really
non-bootstrap-specific.
Stefan
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
prev parent reply other threads:[~2002-03-26 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E16oZ1I-0001u2-00@fencepost.gnu.org>
2002-03-23 9:53 ` Emacs-diffs digest, Vol 1 #508 - 12 msgs Eli Zaretskii
2002-03-25 16:29 ` Stefan Monnier
2002-03-25 20:10 ` Eli Zaretskii
2002-03-25 22:40 ` Stefan Monnier
2002-03-26 5:58 ` Eli Zaretskii
2002-03-26 15:31 ` Stefan Monnier [this message]
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=200203261531.g2QFVRR17627@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@gnu.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 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).