From: Stefan Kangas <stefankangas@gmail.com>
To: Akib Azmain Turja <akib@disroot.org>
Cc: 59340@debbugs.gnu.org, eliz@gnu.org, akrl@sdf.org
Subject: bug#59340: 29.0.50; Latest Emacs from master gives various native compilation errors
Date: Thu, 24 Nov 2022 10:27:24 -0800 [thread overview]
Message-ID: <CADwFkmkeM-ecK27sPc3EsTUdYZ10KjRcb-pjEhxAG3xOVT5g0Q@mail.gmail.com> (raw)
In-Reply-To: <87k03mylf3.fsf@disroot.org> (Akib Azmain Turja's message of "Tue, 22 Nov 2022 23:00:00 +0600")
Akib Azmain Turja <akib@disroot.org> writes:
>> 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!
Should this bug remain open?
next prev parent reply other threads:[~2022-11-24 18:27 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
2022-11-24 18:27 ` Stefan Kangas [this message]
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=CADwFkmkeM-ecK27sPc3EsTUdYZ10KjRcb-pjEhxAG3xOVT5g0Q@mail.gmail.com \
--to=stefankangas@gmail.com \
--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.