unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sam Steingold <sds@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bootstrap problems on w32
Date: Mon, 31 Jan 2011 23:30:32 +0200	[thread overview]
Message-ID: <83aaigg3rb.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTinfZroAA-m8+PxUd_o9Ag4KOzxmMqgwW840JS7X@mail.gmail.com>

> Date: Mon, 31 Jan 2011 15:08:21 -0500
> From: Sam Steingold <sds@gnu.org>
> Cc: emacs-devel@gnu.org
> 
> On Mon, Jan 31, 2011 at 2:47 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Request granted (revision 103055).
> 
> I seem to be getting emacs built (thanks a lot!), but I also get these:
> 
> "./oo-spd/i386/emacs.exe" -batch -f list-load-path-shadows
> Warning: Could not find simple.el nor simple.elc
> Cannot open load file: shadow
> make[1]: [oo-spd/i386/emacs.exe] Error 127 (ignored)
> 
> and then:
> 
> make[1]: Entering directory `/cygdrive/c/sds/src/emacs/trunk/leim'
> "./../src/oo-spd/i386/emacs.exe" -batch --no-site-file --no-site-lisp
> -f batch-byte-compile quail/py-punct.el
> Warning: Could not find simple.el nor simple.elc
> Cannot open load file: bytecomp
> make[1]: *** [quail/py-punct.elc] Error 127

I've just did a full bootstrap with the current trunk, and I don't see
any such problems.  It ran to completion without a hitch.

So perhaps this is some local problem on that machine.



      parent reply	other threads:[~2011-01-31 21:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 10:27 Bootstrap problems on w32 B. Anyos
2011-01-29 12:57 ` Eli Zaretskii
2011-01-31 15:02   ` Sam Steingold
2011-01-31 15:15     ` Eli Zaretskii
2011-01-31 17:47       ` Sam Steingold
2011-01-31 19:47         ` Eli Zaretskii
2011-01-31 20:08           ` Sam Steingold
2011-01-31 20:15             ` Eli Zaretskii
2011-01-31 20:19               ` Sam Steingold
2011-01-31 20:47                 ` Eli Zaretskii
2011-01-31 21:30             ` Eli Zaretskii [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=83aaigg3rb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sds@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).