From: Robin Templeton <robin@terpri.org>
To: guile-devel@gnu.org
Subject: Re: Guile 3 and wip-elisp/Emacs
Date: Thu, 21 Oct 2021 13:49:22 -0400 [thread overview]
Message-ID: <8735oumfod.fsf@terpri.org> (raw)
In-Reply-To: 47-61683800-21-6332ae00@62794253
"Gregg Sangster" <gregg@thesangsters.ca> writes:
> Hello,
>
> I have wip-elisp rebased all the way up to main as of a few days ago
> (e60469c8b6936575c079faaffa40a340e1d49f3c) plus two changes from
> Ricardo. It's available here:
>
> https://git.sr.ht/~g20r/guile
>
> There is one test failure in "make check" on test-out-of-memory. I
> haven't investigated it yet but I get the same failure on main. If
> that's not an expected failure, it might be a problem with my
> environment.
>
> There is also an emacs repo here:
>
> https://git.sr.ht/~g20r/emacs
>
> which uses the 3.0-based wip-elisp. It builds and runs but segfaults
> easily. I've started rebasing it on a more current emacs. Those
> changes aren't published yet.
It's not a good sign that it segfaults easily; Someone(TM) should figure
out the source of the crashes even if rebasing happens to fix them,
which I wouldn't necessarily count on. I'll try to do some debugging in
the next few days.
> I haven't been able to get the guile-emacs package in guix working. The
> build gets stuck at collecting/processing OKURI-NASI entries after a few
> hours. For comparison, the 3.0-based guile-emacs builds in about 20
> minutes on my machine. If anyone has that running, it would be nice to
> have a comparison of the build/run speed.
I can confirm that, it seems to get stuck at:
Reading file "/tmp/guix-build-[...]/[...]/leim/SKK-DIC/SKK-JISYO.L" ...
[...]
Collecting OKURI-NASI entries ...
[...]
collected 70% ...
even after running for quite a while:
guix build -c32 guile-emacs 5.29s user 0.47s system 0% cpu 28:02:53.21 total
I'm not sure what's going on here, as I've definitely installed the
guile-emacs package before (though not recently) and it doesn't use the
standard emacs and guile packages, for obvious reasons. I can probably
use guix time-machine to figure out what's happening. That build phase
was always excruciatingly slow, but not *that* slow.
--
„Die Philosophen haben die Welt nur verschieden *interpretiert*, es
kömmt drauf an, sie zu *verändern*.“ -- Karl Marx
next prev parent reply other threads:[~2021-10-21 17:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 15:12 Guile 3 and wip-elisp/Emacs Gregg Sangster
2021-09-10 19:59 ` Dr. Arne Babenhauserheide
2021-09-13 2:13 ` Christine Lemmer-Webber
2021-10-14 14:01 ` Gregg Sangster
2021-10-14 17:34 ` Ricardo Wurmus
2021-10-20 10:56 ` Gregg Sangster
2021-10-21 14:05 ` Ricardo Wurmus
2021-10-21 17:49 ` Robin Templeton [this message]
2021-10-20 11:59 ` Robin Templeton
2021-09-13 10:56 ` Ricardo Wurmus
2021-09-20 10:39 ` Gerry Agbobada
2021-10-14 13:35 ` Gregg Sangster
2021-10-16 5:25 ` Christine Lemmer-Webber
2021-10-19 21:59 ` Christine Lemmer-Webber
2021-10-19 22:29 ` Ludovic Courtès
2021-10-20 1:46 ` Christine Lemmer-Webber
2021-10-20 2:51 ` Christine Lemmer-Webber
2021-10-20 16:27 ` Christopher Allan Webber
2021-10-22 16:11 ` Christine Lemmer-Webber
2021-10-22 16:17 ` Christine Lemmer-Webber
2021-10-22 18:38 ` Gregg Sangster
2021-10-21 19:34 ` Robin Templeton
2021-10-22 2:59 ` Christine Lemmer-Webber
2021-10-20 10:43 ` Gregg Sangster
2021-10-20 11:43 ` Robin Templeton
-- strict thread matches above, loose matches on Subject: below --
2021-09-10 15:09 Gregg Sangster
2021-09-10 15:09 Gregg Sangster
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735oumfod.fsf@terpri.org \
--to=robin@terpri.org \
--cc=guile-devel@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.
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).