From: Philip McGrath <philip@philipmcgrath.com>
To: Jack Hill <jackhill@jackhill.us>,
racket-users@googlegroups.com, 47064@debbugs.gnu.org
Subject: bug#47064: [racket-users] bytevector-uncompress: internal error uncompressing
Date: Mon, 15 Mar 2021 18:38:36 -0400 [thread overview]
Message-ID: <53940c03-4f40-3954-0cb4-3d4ae01c39a2@philipmcgrath.com> (raw)
In-Reply-To: <79c97b4c-defb-3966-dc50-a79fa8f5c053@philipmcgrath.com>
Aha! Running:
guix environment --ad-hoc --no-grafts racket -- drracket
launches DrRacket just fine.
My guess is that Racket CS is compressing string literals in compiled
code. Currently, Guix patches Racket source files to include the
absolute paths to foreign libraries in the store as string literals.
There are a bunch of grafts for GTK and such: if I'm right, Guix somehow
mangles the compiled code while attempting to apply the grafts.
I already thought this strategy was a bad idea. If it is really the
problem, I should be able to patch it fairly quickly: I've already been
experimenting along these lines.
-Philip
next prev parent reply other threads:[~2021-03-15 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.21.2103150040230.8138@marsh.hcoop.net>
2021-03-15 21:38 ` bug#47064: [racket-users] bytevector-uncompress: internal error uncompressing Philip McGrath
2021-03-15 22:26 ` Philip McGrath
2021-03-15 22:38 ` Philip McGrath [this message]
2021-03-16 0:28 ` jackhill
2021-03-16 3:01 ` Philip McGrath
2021-04-14 5:54 ` Mark H Weaver
2021-04-14 22:03 ` Philip McGrath
2021-04-15 8:44 ` Mark H Weaver
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=53940c03-4f40-3954-0cb4-3d4ae01c39a2@philipmcgrath.com \
--to=philip@philipmcgrath.com \
--cc=47064@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
--cc=racket-users@googlegroups.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).