all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Juanma Barranquero" <lekktu@gmail.com>,
	Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: sh.exe needed to bootstrap on Windows?
Date: Mon, 16 Jul 2007 23:19:46 +0300	[thread overview]
Message-ID: <uhco4rti5.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b0707161254q4b5bdc2exb55f7fa7292224db@mail.gmail.com> (lekktu@gmail.com)

> Date: Mon, 16 Jul 2007 21:54:25 +0200
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: emacs-devel@gnu.org
> 
> > If this doesn't help, please run this command under a debugger, put a
> > breakpoint where this error message is printed (in callproc.c and
> > process.c), and show the backtrace when one of these breakpoints
> > breaks.
> 
> Will try.

Okay, I can reproduce this myself, except that in my case it complains
about cmdproxy, like someone else already reported today.  I can
understand why it doesn't find cmdproxy: it's the first pass of
bootstrap, so no binary is yet built except bootstrap-emacs.  But why
does it fail to find sh.exe in your case?  Do you even have sh.exe?
(I do, but I renamed it for this test, because I thought you were
running without sh.exe.)

I think the problem happens because of this change:

    2007-07-16  Dan Nicolaescu  <dann@ics.uci.edu>

	    * vc-hooks.el (vc-handled-backends): Move BZR later in the list.

Dan, can you explain why this change was made?

  reply	other threads:[~2007-07-16 20:19 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16  9:10 sh.exe needed to bootstrap on Windows? Juanma Barranquero
2007-07-16 19:15 ` Eli Zaretskii
2007-07-16 19:54   ` Juanma Barranquero
2007-07-16 20:19     ` Eli Zaretskii [this message]
2007-07-16 20:28       ` Juanma Barranquero
2007-07-16 20:46         ` Eli Zaretskii
2007-07-16 21:01           ` Dan Nicolaescu
2007-07-16 21:19             ` Eli Zaretskii
2007-07-16 21:30               ` Dan Nicolaescu
2007-07-16 22:01                 ` Eli Zaretskii
2007-07-16 22:40                   ` Dan Nicolaescu
2007-07-16 22:44                     ` Eli Zaretskii
2007-07-16 22:53                       ` Dan Nicolaescu
2007-07-17  3:15                         ` Eli Zaretskii
2007-07-16 20:34       ` Dan Nicolaescu
2007-07-17  7:56       ` Jason Rumney
2007-07-17  8:43         ` Dan Nicolaescu
2007-07-17 11:26         ` Eli Zaretskii
2007-07-17 11:39           ` Juanma Barranquero
2007-07-17 11:45           ` Andreas Schwab
2007-07-17 12:51             ` Thien-Thi Nguyen
2007-07-17 13:13               ` David Kastrup
2007-07-17 20:02               ` Eli Zaretskii
2007-07-17 20:03             ` Eli Zaretskii
2007-07-17 16:52           ` Stefan Monnier
2007-07-17 20:06             ` Eli Zaretskii
2007-07-17 22:11               ` Juanma Barranquero
2007-07-16 22:47 ` Eli Zaretskii
2007-07-17 10:07   ` Juanma Barranquero
2007-07-17 10:33     ` 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=uhco4rti5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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.