all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Akib Azmain Turja via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59340@debbugs.gnu.org
Subject: bug#59340: 29.0.50; Latest Emacs from master gives various native compilation errors
Date: Fri, 18 Nov 2022 17:39:11 +0600	[thread overview]
Message-ID: <87leo8wkyo.fsf@disroot.org> (raw)
In-Reply-To: <83h6yxcppr.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 17 Nov 2022 22:04:32 +0200")

[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Fri, 18 Nov 2022 01:08:36 +0600
>> From:  Akib Azmain Turja via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>> 
>> I tried to upgrade to the commit
>> 1772d88c1fa811eee235ba9b8b7584bb000ac293 (made yesterday).  But after
>> installing it, I tried to run to and got various sorts of native
>> compilation errors.  I can at least use it the terminal, but starting
>> with EXWM makes it crash (I don't who is the culprit: EXWM or GTK+).
>> 
>> This also happened to me before when I tried to upgrade, but I didn't do
>> anything, because I'm lazy.
>> 
>> I have reverted to my old Emacs (this) after I encountered the bug.
>> 
>> I clearly remember two things appearing repeatedly in the *Warning*
>> buffer (in terminal), the first one "libgccjit.so: error: error invoking
>> gcc driver", and second one "FILE: Error: Internal native compiler error
>> failed to compile."
>> 
>> The *Async-native-compile-log* buffer says that ld can't find
>> crtbeginS.o, -lgcc, -lgcc_s and -lgcc_s again.  And the message again:
>> "libgccjit.so: error: error invoking gcc driver".
>
> Does this happen _after_ you build Emacs?  That is, you are saying
> that the *.eln files produced as part of the Emacs build were compiled
> successfully, but when you then start the Emacs you built, it is
> unable to perform any native compilation?

Yes, Emacs builds fine.  The problem occurs at runtime.

>
> In any case, I don't see it here.
>
> Could it be that there was some change in your GCC/Binutis/libgccjit
> installation in parallel with updating from the Emacs Git repository?
> That's what the error messages seem to convey.
>
>
>

-- 
Akib Azmain Turja, GPG key: 70018CE5819F17A3BBA666AFE74F0EFA922AE7F5
Fediverse: akib@hostux.social
Codeberg: akib
emailselfdefense.fsf.org | "Nothing can be secure without encryption."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2022-11-18 11:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 19:08 bug#59340: 29.0.50; Latest Emacs from master gives various native compilation errors Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-17 20:04 ` Eli Zaretskii
2022-11-18  9:01   ` Andrea Corallo
2022-11-18 11:23     ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-18 11:39   ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-18 12:06     ` Eli Zaretskii
2022-11-18 15:09       ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-18 15:12         ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-18 16:28           ` Robert Pluim
2022-11-18 16:56         ` Eli Zaretskii
2022-11-18 20:06         ` Andrea Corallo
2022-11-19  4:23           ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-22 17:00             ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-24 18:27               ` Stefan Kangas
2023-06-05 22:17                 ` Andrea Corallo

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87leo8wkyo.fsf@disroot.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=59340@debbugs.gnu.org \
    --cc=akib@disroot.org \
    --cc=eliz@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.