From: "Thompson, David" <dthompson2@worcester.edu>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 57878@debbugs.gnu.org, Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: bug#57878: Minimal reproducible setup
Date: Sat, 1 Oct 2022 20:15:50 -0400 [thread overview]
Message-ID: <CAJ=RwfbckEBc+7MSTbVtKsoL7EGM_ZYk+CecO-6x0PGDkWfntw@mail.gmail.com> (raw)
In-Reply-To: <m1r107iw6t.fsf@fastmail.net>
Hello Konrad and Liliana,
On Mon, Sep 19, 2022 at 5:16 AM Konrad Hinsen
<konrad.hinsen@fastmail.net> wrote:
>
> I did one more test: run native-compile by hand on each elisp file in
> the package ido-completing-read+. Works fine.
>
> The next question that I consider relevant: is this an upstream (Emacs)
> issue, or an issue created by packaging in Guix? That's not easy to
> answer.
I just got bit by this and lost a bunch of time trying to get my
system stable again. I am leaning towards this being an upstream
issue as it is also affecting Debian users [0]. Unfortunately, they
do not seem to have found a solution. I haven't checked the Emacs bug
tracker/mailing lists so I don't know if upstream is working on or has
a fix for this. I will be sticking to a pre-commit
dbcba75c0e96d8eb2b0bf9dbb3a49d15b38f80d2 version of Guix for the time
being. There may be many more people affected that have not reported
in. Is disabling native compilation an option on the table?
- Dave
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017817
next prev parent reply other threads:[~2022-10-02 0:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 9:09 bug#57878: Emacs native compilation on startup can crash the system Konrad Hinsen
2022-09-17 10:28 ` bug#57878: Minimal reproducible setup Konrad Hinsen
2022-09-17 15:45 ` Konrad Hinsen
2022-09-17 23:19 ` Liliana Marie Prikler
2022-09-18 18:35 ` Liliana Marie Prikler
2022-09-19 6:04 ` Konrad Hinsen
2022-09-19 8:51 ` Konrad Hinsen
2022-10-02 0:15 ` Thompson, David [this message]
2022-10-02 0:23 ` Liliana Marie Prikler
2022-10-02 8:25 ` Konrad Hinsen
2022-10-12 19:42 ` Liliana Marie Prikler
2022-10-13 9:31 ` Max Brieiev
2022-10-13 18:23 ` Liliana Marie Prikler
2022-10-14 16:07 ` zimoun
2022-10-14 18:22 ` Liliana Marie Prikler
2022-10-15 10:11 ` zimoun
2022-10-15 14:40 ` Liliana Marie Prikler
2022-10-15 15:40 ` zimoun
2022-10-15 16:30 ` Liliana Marie Prikler
2022-10-25 16:23 ` Max Brieiev
2022-10-25 18:31 ` Liliana Marie Prikler
2022-10-26 7:46 ` zimoun
2022-10-11 10:04 ` zimoun
2022-10-13 10:06 ` Max Brieiev
2023-10-12 14:50 ` bug#57878: Emacs native compilation on startup can crash the system Ludovic Courtès
2023-10-14 14:37 ` Konrad Hinsen
2022-12-09 14:30 ` bug#57878: Some further investigation Konrad Hinsen
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ=RwfbckEBc+7MSTbVtKsoL7EGM_ZYk+CecO-6x0PGDkWfntw@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=57878@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=liliana.prikler@gmail.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/guix.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).