unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dhruva <dhruvakm@gmail.com>
Cc: emacs-pretest-bug@gnu.org, jasonr@gnu.org
Subject: Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional
Date: Wed, 15 Aug 2007 06:19:01 +0300	[thread overview]
Message-ID: <uk5rxcwnu.fsf@gnu.org> (raw)
In-Reply-To: <e3f230850708141803p671decbg997532a2021704fa@mail.gmail.com> (message from dhruva on Wed, 15 Aug 2007 06:33:48 +0530)

> Date: Wed, 15 Aug 2007 06:33:48 +0530
> From: dhruva <dhruvakm@gmail.com>
> Cc: jasonr@gnu.org, emacs-pretest-bug@gnu.org
> 
> Apologies for not providing the complete information. When I keep
> updating from CVS/HG repo, I do an explicit 'recompile'.

In that case, there should be no problem.  After a "make bootstrap",
you are supposed to run "make install", which copies the dumped
emacs.exe into bin.  And if you run "make recompile" after syncing
with CVS and "make" rebuilds emacs.exe, just say this:

    make recompile EMACS=../src/oo-spd/i386/emacs.exe

As Jason pointed out it is wrong to leave bootstrap emacs.exe around,
but the subsequent "make install" should solve that.

  reply	other threads:[~2007-08-15  3:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14 11:21 Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional Christoph Conrad
2007-08-14 12:31 ` Jason Rumney
2007-08-14 12:47   ` Christoph Conrad
2007-08-14 14:40     ` Jason Rumney
2007-08-14 15:19       ` dhruva
2007-08-14 15:28         ` dhruva
2007-08-14 15:39           ` Jason Rumney
2007-08-14 16:43             ` dhruva
2007-08-14 19:33               ` Eli Zaretskii
2007-08-15  1:03                 ` dhruva
2007-08-15  3:19                   ` Eli Zaretskii [this message]
2007-08-15  8:19                     ` dhruva
2007-08-15 18:07                       ` Eli Zaretskii
2007-08-16  2:55                         ` dhruva
2007-08-14 20:01               ` Jason Rumney
2007-08-15  8:12           ` Christoph Conrad
2007-08-15  7:42       ` Christoph Conrad

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=uk5rxcwnu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dhruvakm@gmail.com \
    --cc=emacs-pretest-bug@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 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).