unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* GCC 13.1: Can't build Emacs with Msys2/MinGW64
@ 2023-05-07 14:31 Arash Esbati
  2023-05-07 14:40 ` Eli Zaretskii
  0 siblings, 1 reply; 7+ messages in thread
From: Arash Esbati @ 2023-05-07 14:31 UTC (permalink / raw)
  To: emacs-devel

Hi all,

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.

Best, Arash



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 13.1: Can't build Emacs with Msys2/MinGW64
  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
  0 siblings, 2 replies; 7+ messages in thread
From: Eli Zaretskii @ 2023-05-07 14:40 UTC (permalink / raw)
  To: Arash Esbati; +Cc: emacs-devel

> 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?



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 13.1: Can't build Emacs with Msys2/MinGW64
  2023-05-07 14:40 ` Eli Zaretskii
@ 2023-05-07 14:43   ` Eli Zaretskii
  2023-05-07 17:13   ` Arash Esbati
  1 sibling, 0 replies; 7+ messages in thread
From: Eli Zaretskii @ 2023-05-07 14:43 UTC (permalink / raw)
  To: arash; +Cc: emacs-devel

> Date: Sun, 07 May 2023 17:40:57 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
> 
> >     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?

Also, did you try building a completely fresh clone of the repository?



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 13.1: Can't build Emacs with Msys2/MinGW64
  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
  1 sibling, 1 reply; 7+ messages in thread
From: Arash Esbati @ 2023-05-07 17:13 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

Eli Zaretskii <eliz@gnu.org> writes:

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

This is the tree I always used to build Emacs which worked with older
versions of GCC and libgccjit; last successful build was 605414d018;
currently my tree is up-to-date with commit d5ab8b6f24.  I haven't
reverted GCC or Emacs yet, I will start playing with it now.

In your other mail, you wrote:

> Also, did you try building a completely fresh clone of the repository?

I tried it (d5ab8b6f24).  It says:

    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

And while we're at it: Shouldn't 'git clean -fdx' give me the same state
as a fresh clone?

Best, Arash



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 13.1: Can't build Emacs with Msys2/MinGW64
  2023-05-07 17:13   ` Arash Esbati
@ 2023-05-07 18:28     ` Eli Zaretskii
  2023-05-07 18:39       ` Eli Zaretskii
  0 siblings, 1 reply; 7+ messages in thread
From: Eli Zaretskii @ 2023-05-07 18:28 UTC (permalink / raw)
  To: Arash Esbati; +Cc: emacs-devel

> From: Arash Esbati <arash@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Sun, 07 May 2023 19:13:52 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Does the same tree build OK with older versions of GCC and libgccjit?
> 
> This is the tree I always used to build Emacs which worked with older
> versions of GCC and libgccjit; last successful build was 605414d018;
> currently my tree is up-to-date with commit d5ab8b6f24.  I haven't
> reverted GCC or Emacs yet, I will start playing with it now.
> 
> In your other mail, you wrote:
> 
> > Also, did you try building a completely fresh clone of the repository?
> 
> I tried it (d5ab8b6f24).  It says:
> 
>     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?

> And while we're at it: Shouldn't 'git clean -fdx' give me the same state
> as a fresh clone?

I don't trust that 110%, so a fresh clone is more reliable.




^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 13.1: Can't build Emacs with Msys2/MinGW64
  2023-05-07 18:28     ` Eli Zaretskii
@ 2023-05-07 18:39       ` Eli Zaretskii
  2023-05-08  9:26         ` Arash Esbati
  0 siblings, 1 reply; 7+ messages in thread
From: Eli Zaretskii @ 2023-05-07 18:39 UTC (permalink / raw)
  To: arash, Andrea Corallo; +Cc: emacs-devel

> 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.



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 13.1: Can't build Emacs with Msys2/MinGW64
  2023-05-07 18:39       ` Eli Zaretskii
@ 2023-05-08  9:26         ` Arash Esbati
  0 siblings, 0 replies; 7+ messages in thread
From: Arash Esbati @ 2023-05-08  9:26 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: Andrea Corallo, emacs-devel

Eli Zaretskii <eliz@gnu.org> writes:

> 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.

Done, bug#63365.  Yes, hopefully Andrea has some insight.

Best, Arash



^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2023-05-08  9:26 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2023-05-08  9:26         ` Arash Esbati

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).