From: martin rudalics <rudalics@gmx.at>
To: Juanma Barranquero <lekktu@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Failure to bootstrap on Windows
Date: Fri, 02 Oct 2015 10:37:39 +0200 [thread overview]
Message-ID: <560E4253.3050103@gmx.at> (raw)
In-Reply-To: <CAAeL0SR0uwt_O6ReFnc-18h=vhFoKEcnHH_t2KZz8x+uXsr8=A@mail.gmail.com>
> 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
> Makefile:508: recipe for target 'emacs.exe' failed
> make[1]: *** [emacs.exe] Error -1
> make[1]: Leaving directory 'c:/devel/emacs/repo/trunk/src'
> Makefile:398: recipe for target 'src' failed
> make: *** [src] Error 2
>
>
> Is this a known problem?
Obviously Andy encountered it when filing bug#16047. And I could swear
that I too saw it once. But I hardly ever bootstrap.
martin
next prev parent reply other threads:[~2015-10-02 8:37 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
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 [this message]
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
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=560E4253.3050103@gmx.at \
--to=rudalics@gmx.at \
--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 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).