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

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



  parent reply	other threads:[~2023-05-07 17:13 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 [this message]
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=86ttwoawtr.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=eliz@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).