From: Akib Azmain Turja via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 59340@debbugs.gnu.org
Cc: eliz@gnu.org, akrl@sdf.org
Subject: bug#59340: 29.0.50; Latest Emacs from master gives various native compilation errors
Date: Tue, 22 Nov 2022 23:00:00 +0600 [thread overview]
Message-ID: <87k03mylf3.fsf@disroot.org> (raw)
In-Reply-To: <874juvpo7f.fsf@disroot.org> (Akib Azmain Turja via's message of "Sat, 19 Nov 2022 10:23:16 +0600")
[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]
Akib Azmain Turja via "Bug reports for GNU Emacs, the Swiss army knife
of text editors" <bug-gnu-emacs@gnu.org> writes:
> Andrea Corallo <akrl@sdf.org> writes:
>
>> Akib Azmain Turja via "Bug reports for GNU Emacs, the Swiss army knife
>> of text editors" <bug-gnu-emacs@gnu.org> writes:
>>
>>> --=-=-=
>>> Content-Type: text/plain
>>> Content-Transfer-Encoding: quoted-printable
>>>
>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>
>>>>> From: Akib Azmain Turja <akib@disroot.org>
>>>>> Cc: 59340@debbugs.gnu.org
>>>>> Date: Fri, 18 Nov 2022 17:39:11 +0600
>>>>>=20
>>>>> > 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?
>>>>>=20
>>>>> Yes, Emacs builds fine. The problem occurs at runtime.
>>>>
>>>> That is very strange, because we invoke libgccjit and Binutils during
>>>> the build the same we do at run time. Is this in "emacs -Q"? If not,
>>>> perhaps some of your customizations prevent Emacs from finding and/or
>>>> invoking the JIT compiler?
>>>
>>> I think this is not an Emacs bug really. The Guix recipe I'm using
>>> has some big problems (according to Guix philosophy), and probably does
>>> some (black) magic that causes the build and run-time environment to be
>>> different, thus the error.
>>>
>>> However, why the crash? Is it somehow because the old eln get loaded?
>>
>> Are you sure Emacs is crashing? That would be surprising to me, maybe
>> is because of something with EXWM that gets stuck for some other reason?
>>
>> Andrea
>
> I am sure, because instead of running emacs from my .xsession, I ran
> xterm and ran emacs with xterm. The result was, sometimes the Emacs
> aborted, and sometimes segfault.
I have fixed it!
--
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 --]
next prev parent reply other threads:[~2022-11-22 17:00 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
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 [this message]
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=87k03mylf3.fsf@disroot.org \
--to=bug-gnu-emacs@gnu.org \
--cc=59340@debbugs.gnu.org \
--cc=akib@disroot.org \
--cc=akrl@sdf.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.