emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GCC 13.1: Can't build Emacs with Msys2/MinGW64


From: Eli Zaretskii
Subject: Re: GCC 13.1: Can't build Emacs with Msys2/MinGW64
Date: Sun, 07 May 2023 21:28:32 +0300

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]