unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: arash@gnu.org, Andrea Corallo <akrl@sdf.org>
Cc: emacs-devel@gnu.org
Subject: Re: GCC 13.1: Can't build Emacs with Msys2/MinGW64
Date: Sun, 07 May 2023 21:39:14 +0300	[thread overview]
Message-ID: <831qjsdm0d.fsf@gnu.org> (raw)
In-Reply-To: <835y94dmi7.fsf@gnu.org> (message from Eli Zaretskii on Sun, 07 May 2023 21:28:32 +0300)

> Date: Sun, 07 May 2023 21:28:32 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
> 
> >     ELC+ELN  ../lisp/format.elc
> >     ELC+ELN  ../lisp/frame.elc
> > 
> >   Error: wrong-type-argument ("../lisp/frame.el" number-or-marker-p
> >   Backtrace:
> >   00007ff69417a12e
> >   00007ff694048be1
> >   00007ff694069601
> >   ...
> >   make[3]: *** [Makefile:283: ../lisp/frame.elc] Error 3
> >   make[2]: *** [Makefile:842: ../lisp/frame.elc] Error 2
> 
> OK, so this is some real problem with this version of GCC and/or
> libgccjit.  What version of Binutils do you have installed, and was it
> also updated when you installed GCC 13?

I think the next step is to run one of the offending commands under
GDB and show the backtrace from the crash.

The file etc/DEBUG has some advice on debugging problems with
native-compilation.

I add Andrea to this discussion in the hope that he might have ideas
and advice.  And I think you should submit a bug report, so we could
discuss this on the bug tracker, not here.



  reply	other threads:[~2023-05-07 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-07 14:31 GCC 13.1: Can't build Emacs with Msys2/MinGW64 Arash Esbati
2023-05-07 14:40 ` Eli Zaretskii
2023-05-07 14:43   ` Eli Zaretskii
2023-05-07 17:13   ` Arash Esbati
2023-05-07 18:28     ` Eli Zaretskii
2023-05-07 18:39       ` Eli Zaretskii [this message]
2023-05-08  9:26         ` Arash Esbati

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=831qjsdm0d.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=akrl@sdf.org \
    --cc=arash@gnu.org \
    --cc=emacs-devel@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).