all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org, jasonr@gnu.org
Subject: Re: [Emacs-diffs] Changes to emacs/nt/INSTALL,v
Date: Fri, 11 Apr 2008 12:46:03 +0200	[thread overview]
Message-ID: <f7ccd24b0804110346y7e838fbfi2b8bf6b7cda83774@mail.gmail.com> (raw)
In-Reply-To: <umyo0adxj.fsf@gnu.org>

On Fri, Apr 11, 2008 at 12:22 PM, Eli Zaretskii <eliz@gnu.org> wrote:

>  > Hm. I would've said that the whole point of cvs-update is to be more
>  > correct than recompile; else, why not simply use recompile, which is
>  > faster?
>
>  Because without the other prerequisites of cvs-update, especially
>  autoloads, you will have a buggy Emacs.

I thought that was implied in "to be more correct than recompile" ;-)

>  It's the same hardware, so maybe half an hour is so long for me that I
>  took it for three times that ;-)  I don't really remember how long it
>  was exactly, but it seemed forever.

Oh, I usually do (in a .BAT)

   cvs update
   cd nt
   make maintainer-clean  ; realclean before
   configure
   make bootstrap install

as the first thing in the morning, and I let it happily compile. Time
is not much of an issue, I use 22.X meanwhile.

>  I never do a "make recompile" from the nt subdirectory.

I don't, either (I use cvs-update from lisp/), but as of yesterday,
nt/INSTALL includes this:

  make recompile
  Recompiles any changed lisp files after a cvs update.  This saves
  doing a full bootstrap after every update.  If this or a subsequent
  make fail, you probably need to perform a full bootstrap, though
  running this target multiple times may eventually sort out the
  interdependencies.

so it would be perhaps preferable for recompile (from nt/) to do a bit
more work and be more correct.

Just a nitpick, though.

   Juanma




  reply	other threads:[~2008-04-11 10:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Jjscj-0002sL-1T@cvs.savannah.gnu.org>
2008-04-10  9:36 ` [Emacs-diffs] Changes to emacs/nt/INSTALL,v Juanma Barranquero
2008-04-10  9:50   ` Jason Rumney
2008-04-10 17:53     ` Recommended build procedure [was Re: [Emacs-diffs] Changes to emacs/nt/INSTALL, v] Glenn Morris
2008-04-10 19:52   ` [Emacs-diffs] Changes to emacs/nt/INSTALL,v Eli Zaretskii
2008-04-10 20:21     ` Jason Rumney
2008-04-10 22:24     ` Juanma Barranquero
2008-04-11  8:43       ` Eli Zaretskii
2008-04-11  9:13         ` Juanma Barranquero
2008-04-11 10:22           ` Eli Zaretskii
2008-04-11 10:46             ` Juanma Barranquero [this message]
2008-04-11 14:40               ` 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

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

  git send-email \
    --in-reply-to=f7ccd24b0804110346y7e838fbfi2b8bf6b7cda83774@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@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 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.