unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: GCC 13.1: Can't build Emacs with Msys2/MinGW64
Date: Sun, 07 May 2023 17:40:57 +0300	[thread overview]
Message-ID: <83a5ygdx1i.fsf@gnu.org> (raw)
In-Reply-To: <86r0rs8b6r.fsf@gnu.org> (message from Arash Esbati on Sun, 07 May 2023 16:31:56 +0200)

> From: Arash Esbati <arash@gnu.org>
> Date: Sun, 07 May 2023 16:31:56 +0200
> 
> GCC 13.1 landed on my HD and I can't build Emacs (both release branch
> and master) anymore.  This happens only when I pass
> --with-native-compilation to configure.  In summary:
> 
>   $ git clean -fdx --exclude=ChangeLog
>   $ ./autogen.sh
>   $ ./configure --without-native-compilation
>   $ make
> 
> works and
> 
>   $ git clean -fdx --exclude=ChangeLog
>   $ ./autogen.sh
>   $ ./configure --with-native-compilation
>   $ make
> 
> breaks during compilation with
> 
>     ELC      dired.elc
>     ELC      dired-aux.elc
>     ELC      dired-loaddefs.elc
>     ELC      dired-x.elc
> 
>   Backtrace:
>   00007ff7de14a69e
>   00007ff7de018b21
>   00007ff7de039541
>   00007ff7de1aedaa
>   00007ff9b7977ff0
>   00007ff9b81b23d7
>   00007ff9b816149c
>   00007ff9b81b0f06
>   00007ff7de09ea80
>   ...
>   make[3]: *** [Makefile:327: dired-x.elc] Error 3
> 
> and others warnings like the above.  
> 
> Before digging more into it and possibly filing a bug report, do
> others observe the same issue?  This is on Win10 with Msys2/MinGW64,
> gcc.exe (Rev4, Built by MSYS2 project) 13.1.0.

Does the same tree build OK with older versions of GCC and libgccjit?



  reply	other threads:[~2023-05-07 14:40 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 [this message]
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
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=83a5ygdx1i.fsf@gnu.org \
    --to=eliz@gnu.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).