From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Emacs Development <emacs-devel@gnu.org>,
martin rudalics <rudalics@gmx.at>
Subject: Re: Building master fails on Windows 10 when testing etc/NEWS file
Date: Wed, 18 Sep 2019 19:54:05 +0100 [thread overview]
Message-ID: <CAPM58ogN+B9qzLxpHZsX-F1Nkh2Q42ZijW9xHY0jJjnPDdBaTg@mail.gmail.com> (raw)
In-Reply-To: <83sgottp6w.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]
On Wed, 18 Sep 2019 at 19:49, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Richard Copley <rcopley@gmail.com>
> > Date: Wed, 18 Sep 2019 19:35:31 +0100
> > Cc: Juanma Barranquero <lekktu@gmail.com>, Paul Eggert <
> eggert@cs.ucla.edu>,
> > martin rudalics <rudalics@gmx.at>, Emacs Development <
> emacs-devel@gnu.org>
> >
> > Thread 1 hit Breakpoint 2, Fload (file=XIL(0x40123a4), noerror=XIL(0),
> nomessage=XIL(0x30), nosuffix=XIL
> > (0), must_suffix=XIL(0x30)) at lread.c:1437
> > 1437 report_file_error ("Opening stdio stream", file);
> >
> > Thread 5 (Thread 19220.0x778):
> > #0 0x00007ffd293ceae4 in ntdll!ZwDelayExecution () from
> C:\WINDOWS\SYSTEM32\ntdll.dll
> > #1 0x00007ffd26881e41 in SleepEx () from
> C:\WINDOWS\System32\KernelBase.dll
> > #2 0x00000004003f026e in timer_loop (arg=0x400929120 <real_itimer>) at
> w32proc.c:473
> > #3 0x00007ffd27e55bb4 in KERNEL32!BaseThreadInitThunk () from
> C:\WINDOWS\System32\kernel32.dll
> > #4 0x00007ffd29389ee1 in ntdll!RtlUserThreadStart () from
> C:\WINDOWS\SYSTEM32\ntdll.dll
> > #5 0x0000000000000000 in ?? ()
> > Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>
> Thanks, but this is the wrong thread...
>
The rest is missing because of the part I was smiling about:
Lisp Backtrace:
"package-activate-all" (0xbfe1c0)
"command-line" (0xbfed38)
"normal-top-level" (0xbff3a0)
Opening stdio stream: No such file or directory, package
> Anyway, the problem should be fixed by now, please try the latest
> master.
>
Works for me. Thanks.
[-- Attachment #2: Type: text/html, Size: 2551 bytes --]
next prev parent reply other threads:[~2019-09-18 18:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 7:45 Building master fails on Windows 10 when testing etc/NEWS file martin rudalics
2019-09-18 10:08 ` Paul Eggert
2019-09-18 10:33 ` Richard Copley
2019-09-18 11:26 ` Paul Eggert
2019-09-18 11:36 ` Juanma Barranquero
2019-09-18 12:23 ` Paul Eggert
2019-09-18 12:31 ` Juanma Barranquero
2019-09-18 12:44 ` Eli Zaretskii
2019-09-18 14:27 ` Richard Copley
2019-09-18 15:01 ` Juanma Barranquero
2019-09-18 15:45 ` Eli Zaretskii
2019-09-18 17:00 ` Richard Copley
2019-09-18 17:23 ` Eli Zaretskii
2019-09-18 18:33 ` Eli Zaretskii
2019-09-18 18:35 ` Richard Copley
2019-09-18 18:49 ` Eli Zaretskii
2019-09-18 18:54 ` Richard Copley [this message]
2019-09-18 18:47 ` Eli Zaretskii
2019-09-18 20:16 ` Paul Eggert
2019-09-19 8:18 ` martin rudalics
2019-09-19 9:53 ` Juanma Barranquero
2019-09-19 9:59 ` Juanma Barranquero
2019-09-18 15:05 ` Eli Zaretskii
2019-09-18 12:33 ` Eli Zaretskii
2019-09-18 12:37 ` Eli Zaretskii
2019-09-19 7:27 ` Paul Eggert
2019-09-18 10:35 ` Juanma Barranquero
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=CAPM58ogN+B9qzLxpHZsX-F1Nkh2Q42ZijW9xHY0jJjnPDdBaTg@mail.gmail.com \
--to=rcopley@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=rudalics@gmx.at \
/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.