unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: andrewgoh2032@yahoo.com
Cc: 74910-done@debbugs.gnu.org
Subject: bug#74910: 3 Warnings or Errors after starting up Emacs 29.4
Date: Sat, 28 Dec 2024 13:34:38 +0200	[thread overview]
Message-ID: <867c7kt50x.fsf@gnu.org> (raw)
In-Reply-To: <86r067pnae.fsf@gnu.org> (message from Eli Zaretskii on Mon, 16 Dec 2024 19:09:45 +0200)

> Cc: 74910@debbugs.gnu.org
> Date: Mon, 16 Dec 2024 19:09:45 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > Date: Mon, 16 Dec 2024 11:39:34 +0000 (UTC)
> > From:  Andrew Goh via "Bug reports for GNU Emacs,
> >  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> > 
> > I get these three warnings after starting Emacs 29.4
> > 
> > a.  Fatal error: no compiled in support for x86-64
> > b.  C:\Program Files\Emacs\emacs-29.4\bin\libgccjit-0.dll: error invoking gcc driver
> > c.  C:/Program Files/Emacs/emacs29.4/share/emacs/29.4/lisp/emacs-lisp/cl.seq-el Error: Internal native
> > compiler error familed to compile
> > 
> > I hope these errors are fixed, and that it Emacs can auto update without the need to run package-update-all
> > which shows how green I am with Emacs.
> 
> Sounds like you have a mix of 32-bit and 64-bit development tools, and
> that causes the problem.  Like, if your libgccjit is 64-bi, but
> Binutils are for 32 bits.
> 
> IOW, this is a configuration problem local to your system, not an
> Emacs bug.

No further comments in 2 weeks, so I'm now closing this bug.





      reply	other threads:[~2024-12-28 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1580712157.2383087.1734349174973.ref@mail.yahoo.com>
2024-12-16 11:39 ` bug#74910: 3 Warnings or Errors after starting up Emacs 29.4 Andrew Goh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-16 17:09   ` Eli Zaretskii
2024-12-28 11:34     ` Eli Zaretskii [this message]

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=867c7kt50x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74910-done@debbugs.gnu.org \
    --cc=andrewgoh2032@yahoo.com \
    /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).