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>
Cc: emacs-devel@gnu.org
Subject: Re: Failure to bootstrap on Windows
Date: Fri, 02 Oct 2015 18:15:13 +0300	[thread overview]
Message-ID: <83k2r55mke.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SSQ1KJXxJiBNVyeS5+9xfEu0rXtku0adPm5GcgNRTcRXw@mail.gmail.com>

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Thu, 1 Oct 2015 23:45:47 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> $ LC_ALL=C ./temacs -batch -l loadup dump
> Loading loadup.el (source)...
> Using load-path (c:/Devel/emacs/repo/trunk/lisp)
> Loading emacs-lisp/byte-run (source)...
> Loading emacs-lisp/backquote (source)...
> Loading subr (source)...
> Loading version (source)...
> Loading widget (source)...
> Loading custom (source)...
> Loading emacs-lisp/map-ynp (source)...
> Loading international/mule (source)...
> Loading international/mule-conf (source)...
> Loading env (source)...
> Loading format (source)...
> Loading bindings (source)...
> Loading window (source)...
> Loading files.el (source)...
> Loading emacs-lisp/macroexp...
> Loading cus-face.el (source)...
> Loading faces.el (source)...
> Loading button.el (source)...
> Loading loaddefs.el (source)...
> Growing hash table to: 105000
> Loading emacs-lisp/nadvice.el (source)...
> Eager macro-expansion failure: (error "Attempt to autoload
> gv--defun-declaration while preparing to dump")
> Eager macro-expansion failure: (error "Attempt to autoload
> gv--defun-declaration while preparing to dump")
> Attempt to autoload gv--defun-declaration while preparing to dump

Actually, something here looks very wrong to me.  From the fact that
all the Lisp files are loaded in source form I conclude that they have
not yet been compiled.  But in that case, the command that should run
is not what you show, it should be this:

  ./temacs --batch --load loadup bootstrap

Also, it shows on my system a much longer load-path:

  ./temacs --batch --load loadup bootstrap
  Loading loadup.el (source)...
  Using load-path (d:/gnu/git/emacs/emacs-test/lisp d:/gnu/git/emacs/emacs-test/lisp/emacs-lisp d:/gnu/git/emacs/emacs-test/lisp/language d:/gnu/git/emacs/emacs-test/lisp/international d:/gnu/git/emacs/emacs-test/lisp/textmodes d:/gnu/git/emacs/emacs-test/lisp/vc)

Finally, the loading report looks somewhat different here:

  Loading emacs-lisp/byte-run (source)...
  Loading emacs-lisp/backquote (source)...
  Loading subr (source)...
  Loading version (source)...
  Loading widget (source)...
  Loading custom (source)...
  Loading emacs-lisp/map-ynp (source)...
  Loading international/mule (source)...
  Loading international/mule-conf (source)...
  Loading env (source)...
  Loading format (source)...
  Loading bindings (source)...
  Loading window (source)...
  Loading d:/gnu/git/emacs/emacs-test/lisp/files.el (source)...
  Loading d:/gnu/git/emacs/emacs-test/lisp/emacs-lisp/macroexp.el (source)...
  Loading d:/gnu/git/emacs/emacs-test/lisp/emacs-lisp/pcase.el (source)...
  Loading d:/gnu/git/emacs/emacs-test/lisp/emacs-lisp/macroexp.el (source)...
  Loading d:/gnu/git/emacs/emacs-test/lisp/cus-face.el (source)...
  Loading d:/gnu/git/emacs/emacs-test/lisp/faces.el (source)...
  Loading d:/gnu/git/emacs/emacs-test/lisp/button.el (source)...
  Loading d:/gnu/git/emacs/emacs-test/lisp/ldefs-boot.el (source)...
  Loading d:/gnu/git/emacs/emacs-test/lisp/emacs-lisp/nadvice.el (source)...
  Loading d:/gnu/git/emacs/emacs-test/lisp/emacs-lisp/cl-preloaded.el (source)...
  Loading d:/gnu/git/emacs/emacs-test/lisp/minibuffer.el (source)...
  ...

(Note that it loads ldefs-boot.el, not loaddefs.el.)  Immediately
after this command, the build proceeds to compile the Lisp files we
preload, including nadvice.el and subr.el (and many others).  When
temacs is run afterwards, it loads the preloaded files in
byte-compiled form, not in source form:

  LC_ALL=C ./temacs -batch -l loadup dump
  Loading loadup.el (source)...
  Using load-path (d:/gnu/git/emacs/emacs-test/lisp)
  Loading emacs-lisp/byte-run...
  Loading emacs-lisp/backquote...
  Loading subr...
  Loading version...
  Loading widget...
  Loading custom...
  Loading emacs-lisp/map-ynp...
  Loading international/mule...
  Loading international/mule-conf...
  Loading env...
  Loading format...
  Loading bindings...
  Loading window...
  Loading files...
  Loading emacs-lisp/macroexp...
  Loading cus-face...
  Loading faces...
  Loading button...
  Loading loaddefs.el (source)...
  Loading emacs-lisp/nadvice...
  Loading emacs-lisp/cl-preloaded...
  Loading minibuffer...
  Loading abbrev...
  Loading simple...
  Loading help...
  Loading jka-cmpr-hook...
  ...

So it sounds like something else, earlier in your build, went wrong
and left the Lisp files un-compiled.  Could you please show the full
transcript of the build, starting with the command "make bootstrap"?
(If it's too long, please send it compressed.)  Perhaps the
compilation using bootstrap-emacs.exe fails for some reason, in which
case we should be investigating that failure.



  parent reply	other threads:[~2015-10-02 15:15 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30  8:29 Failure to bootstrap on Windows Juanma Barranquero
2015-10-01  9:55 ` Eli Zaretskii
2015-10-01 14:07   ` Juanma Barranquero
2015-10-01 16:47     ` Dani Moncayo
2015-10-01 21:34       ` Juanma Barranquero
2015-10-01 17:02     ` Eli Zaretskii
2015-10-01 20:52       ` Juanma Barranquero
2015-10-01 21:01         ` Eli Zaretskii
2015-10-01 21:45           ` Juanma Barranquero
2015-10-02  6:41             ` Eli Zaretskii
2015-10-02  7:13               ` Juanma Barranquero
2015-10-02  8:36                 ` Eli Zaretskii
2015-10-02  9:58                   ` Juanma Barranquero
2015-10-02 10:14                     ` Eli Zaretskii
2015-10-02 10:21                       ` Juanma Barranquero
2015-10-02 15:15             ` Eli Zaretskii [this message]
2015-10-02 15:45               ` Juanma Barranquero
2015-10-02 17:47                 ` Eli Zaretskii
2015-10-02 18:48                   ` Juanma Barranquero
2015-10-02 19:07                     ` Eli Zaretskii
2015-10-02 21:49                       ` Juanma Barranquero
2015-10-03  8:35                         ` Eli Zaretskii
2015-10-03 10:01                           ` Eli Zaretskii
2015-10-03 21:17                           ` Juanma Barranquero
2015-10-04  2:53                             ` Juanma Barranquero
2015-10-04  6:56                               ` Eli Zaretskii
2015-10-04 10:07                                 ` Juanma Barranquero
2015-10-04 10:18                                   ` Werner LEMBERG
2015-10-04 11:00                                     ` Eli Zaretskii
2015-10-04 11:48                                     ` Juanma Barranquero
2015-10-04 10:59                                   ` Eli Zaretskii
2015-10-04 11:51                                     ` Juanma Barranquero
2015-10-04 12:02                                       ` Eli Zaretskii
2015-10-04 14:41                                         ` Stephen Leake
2015-10-04 16:56                                           ` Eli Zaretskii
2015-10-04  6:36                             ` Eli Zaretskii
2015-10-02  8:37 ` martin rudalics
2015-10-02  9:37   ` Juanma Barranquero
2015-10-02  9:52     ` martin rudalics
2015-10-02 13:01     ` Stephen Leake
2015-10-02 13:32       ` Juanma Barranquero
2015-10-02 13:55     ` Eli Zaretskii
2015-10-02 15:02       ` Juanma Barranquero
2015-10-02 15:20         ` Eli Zaretskii
2015-10-02 15:31           ` Juanma Barranquero
2015-10-02 16:23           ` martin rudalics
2015-10-02 18:03             ` Eli Zaretskii
2015-10-03  8:31               ` martin rudalics
2015-10-03 10:00                 ` Eli Zaretskii
2015-10-02 10:04   ` 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=83k2r55mke.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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.