From: jackhill <jackhill@trilug.org>
To: Philip McGrath <philip@philipmcgrath.com>
Cc: 47064@debbugs.gnu.org, racket-users@googlegroups.com
Subject: bug#47064: [racket-users] bytevector-uncompress: internal error uncompressing
Date: Mon, 15 Mar 2021 20:28:31 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2103152026420.8138@marsh.hcoop.net> (raw)
In-Reply-To: <53940c03-4f40-3954-0cb4-3d4ae01c39a2@philipmcgrath.com>
On Mon, 15 Mar 2021, Philip McGrath wrote:
> 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.
Aha, that does sound promising. This certinially wouldn't be the only
grafts corner case:
https://issues.guix.gnu.org/33848
https://issues.guix.gnu.org/30265
Thanks for taking a look,
Jack
next prev parent reply other threads:[~2021-03-16 9:05 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
2021-03-16 0:28 ` jackhill [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2103152026420.8138@marsh.hcoop.net \
--to=jackhill@trilug.org \
--cc=47064@debbugs.gnu.org \
--cc=philip@philipmcgrath.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.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.