all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Lute.Kamstra@cwi.nl, teirllm@dms.auburn.edu,
	Andreas Schwab <schwab@suse.de>,
	eliz@elta.co.il, ats@acm.org, emacs-devel@gnu.org
Subject: Re: References in elisp.dvi.
Date: 24 Oct 2003 10:24:54 -0400	[thread overview]
Message-ID: <jwvn0bqu3dp.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (raw)
In-Reply-To: <E1ACuIk-00035m-BZ@fencepost.gnu.org>

> in make bootstrap, the second make shd create it again.
> that's the way to avoid this error.

BTW, why does bootstrap do all those `clean' steps?  The few times I call
`bootstrap' I find those steps just waste my time by removing and rebuilding
files in the exact same way.  I'd rather call the bootstrap-clean-before
step manually when needed.  It's especially annoying when the bootstrap
fails partway because "fix && make boostrap" will start all over from
scratch each and every time.


        Stefan

  reply	other threads:[~2003-10-24 14:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21 14:50 References in elisp.dvi Lute Kamstra
2003-10-21 15:35 ` Alan Shutko
2003-10-21 17:03   ` Lute Kamstra
2003-10-21 18:20     ` Alan Shutko
2003-10-21 19:02     ` Eli Zaretskii
2003-10-21 20:17       ` Andreas Schwab
2003-10-22  6:10         ` Eli Zaretskii
2003-10-23  9:23         ` Richard Stallman
2003-10-23 10:06           ` Andreas Schwab
2003-10-23 13:00             ` Luc Teirlinck
2003-10-23 13:10               ` Andreas Schwab
2003-10-24  5:15                 ` Richard Stallman
2003-10-24 14:24                   ` Stefan Monnier [this message]
2003-10-23 13:07             ` Luc Teirlinck
2003-10-23 13:17               ` Luc Teirlinck
2003-10-23 13:25               ` Andreas Schwab
2003-10-23  9:23       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvn0bqu3dp.fsf-monnier+emacs/devel@vor.iro.umontreal.ca \
    --to=monnier@iro.umontreal.ca \
    --cc=Lute.Kamstra@cwi.nl \
    --cc=ats@acm.org \
    --cc=eliz@elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@suse.de \
    --cc=teirllm@dms.auburn.edu \
    /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.