From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 30680@debbugs.gnu.org, help-guix <help-guix@gnu.org>,
racket-users@googlegroups.com
Subject: bug#30680: [racket-users] Using Racket's raco on on Guix(SD)
Date: Sat, 11 Aug 2018 11:18:08 -0400 [thread overview]
Message-ID: <87wosxexu7.fsf__9777.30513918704$1534000629$gmane$org@dustycloud.org> (raw)
In-Reply-To: <0990d521-934b-069b-3f29-faf8a22a5bd0@fastmail.net>
Konrad Hinsen writes:
> On 22/05/2018 15:42, Christopher Lemmer Webber wrote:
>
>> Unfortunately when I try to install packages with "raco pkg install"
>> I get errors like the following:
>
> I filed a bug report about this problem a while ago:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30680
>
> Quote:
>
> I traced this back as far as I could by looking at the Racket compiler
> source code. Compilation generates a temporary file in the same
> directory where the result is supposed to go. If no errors occur, the
> temporary file is then renamed to become the output. The partial stack
> traces point to locations in the code that do a recursive traversal of
> a library in order to compile everything. Unfortunately, the part that
> decides where the output goes is not referenced in the stack trace.
>
>> I seem to remember a couple of packages failing altogether, though in
>> the present moment I think the result is bad performance due to not
>> being properly compiled, but I'm not really sure.
>
> In my tests, all packages ended up working, but performance is indeed
> worse than with a Racket installation outside of Guix.
>
> It would be nice if someone with more knowledge of Racket internals
> could give a hint or two for debugging this issue!
>
> Konrad.
I'm posting a bug bounty on this issue: if someone can fix this I will
pay them $250 USD. I don't have the time or knowledge enough of Racket
internals to do so myself.
next parent reply other threads:[~2018-08-11 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87d0xn24d9.fsf@dustycloud.org>
[not found] ` <0990d521-934b-069b-3f29-faf8a22a5bd0@fastmail.net>
2018-08-11 15:18 ` Christopher Lemmer Webber [this message]
[not found] ` <87wosxexu7.fsf@dustycloud.org>
2018-08-11 20:23 ` bug#30680: [racket-users] Using Racket's raco on on Guix(SD) Timothy Sample
[not found] ` <87h8k0d54i.fsf@ngyro.com>
2018-08-11 21:55 ` Christopher Lemmer Webber
[not found] ` <87va8gfu0c.fsf@dustycloud.org>
2018-08-11 22:05 ` Nils Gillmann
[not found] ` <20180811220538.ca2wyilh6gq62dm3@abyayala>
2018-08-11 23:28 ` Christopher Lemmer Webber
[not found] ` <87tvo0fpox.fsf@dustycloud.org>
2018-08-12 2:03 ` Timothy Sample
[not found] ` <871sb4cpeu.fsf@ngyro.com>
2018-08-12 9:32 ` Gábor Boskovits
2018-08-12 15:31 ` Christopher Lemmer Webber
[not found] ` <87r2j3fvor.fsf@dustycloud.org>
2018-08-12 20:44 ` Timothy Sample
[not found] ` <87d0unb9hk.fsf@ngyro.com>
2018-08-13 0:21 ` Christopher Lemmer Webber
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='87wosxexu7.fsf__9777.30513918704$1534000629$gmane$org@dustycloud.org' \
--to=cwebber@dustycloud.org \
--cc=30680@debbugs.gnu.org \
--cc=help-guix@gnu.org \
--cc=konrad.hinsen@fastmail.net \
--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).