From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Max Brieiev <max.brieiev@gmail.com>
Cc: Konrad Hinsen <konrad.hinsen@fastmail.net>,
"Thompson, David" <dthompson2@worcester.edu>,
57878@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: bug#57878: Minimal reproducible setup
Date: Tue, 25 Oct 2022 20:31:58 +0200 [thread overview]
Message-ID: <52f500c6f35520c8b496174bceb9aabbb036682c.camel@gmail.com> (raw)
In-Reply-To: <87ilk7oos1.fsf@gmail.com>
Am Dienstag, dem 25.10.2022 um 19:23 +0300 schrieb Max Brieiev:
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
>
> > Ehm, yes... best to keep this open until I can bump to a version
> > that's
> > approved and solves the problem.
>
> Do the recent changes suppose to fix the issue?
>
> Today I did:
>
> guix pull
> sudo guix system reconfigure /etc/system-config.scm
> guix package -u emacs-next
>
> After starting Emacs I see lots of errors.
>
> It is not mere compilation warnings. They render Emacs unusable,
> because trying to run a command gives me "function is void" errors.
>
> So I switched back to previous generation again.
While I can't really reproduce the one you showed me in a pure
environment, I do see
Warning (comp): /gnu/store/hjciw32mj05yz1m6r6nzwdi12waz81ni-emacs-next-
29.0.50-2.4aeb80c/share/emacs/29.0.50/lisp/emacs-lisp/cl-
loaddefs.el.gz: Error: error Uncompression program `sh' not found
which is equally concerning.
next prev parent reply other threads:[~2022-10-25 18:34 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
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 [this message]
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=52f500c6f35520c8b496174bceb9aabbb036682c.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=57878@debbugs.gnu.org \
--cc=dthompson2@worcester.edu \
--cc=konrad.hinsen@fastmail.net \
--cc=max.brieiev@gmail.com \
--cc=zimon.toutoune@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).