From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Assertion failure !FIXNUM_OVERFLOW_P (lisp_h_make_fixnum_n)
Date: Sun, 18 Aug 2019 17:48:25 +0300 [thread overview]
Message-ID: <83k1bamsw6.fsf@gnu.org> (raw)
In-Reply-To: <1051ca99-9d10-1792-9565-53a1e95d3575@gmx.at> (message from martin rudalics on Sun, 18 Aug 2019 09:44:41 +0200)
> From: martin rudalics <rudalics@gmx.at>
> Date: Sun, 18 Aug 2019 09:44:41 +0200
>
> Building master with MINGW64 currently fails here with the following
> asseertion failure
>
> ../../src/eval.c:1998: Emacs fatal error: assertion failed: !FIXNUM_OVERFLOW_P (lisp_h_make_fixnum_n)
Can you try the current master and see if I succeeded to fix this?
next prev parent reply other threads:[~2019-08-18 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 7:44 Assertion failure !FIXNUM_OVERFLOW_P (lisp_h_make_fixnum_n) martin rudalics
2019-08-18 14:48 ` Eli Zaretskii [this message]
2019-08-19 7:37 ` martin rudalics
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=83k1bamsw6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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 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).