unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: help-guix@gnu.org, "Claes Wallin (韋嘉誠)" <clacke@gmail.com>,
	"Racket Users" <racket-users@googlegroups.com>
Subject: Re: Using Racket's raco on on Guix(SD)
Date: Tue, 22 May 2018 17:01:38 +0200	[thread overview]
Message-ID: <87h8mzoht9.fsf@elephly.net> (raw)
In-Reply-To: <87d0xn24d9.fsf@dustycloud.org>


Christopher Lemmer Webber <cwebber@dustycloud.org> writes:

> Hello all!  Sorry for the cross-post, but I've been doing more
> development in Racket lately from GuixSD... and who wouldn't want a
> scheme-based distribution and a scheme language's tooling to get along
> better?
>
> Unfortunately when I try to install packages with "raco pkg install"
> I get errors like the following:
>
> open-output-file: cannot open output file
>   path: /gnu/store/wnqdzv3f0i86nk3nq15aavpb7kg7fbwx-racket-6.11/share/racket/collects/racket/compiled/tmp15189875891518987589961
>   system error: Read-only file system; errno=30

[…]

“call-with-atomic-output-file” in ’collects/racket/file.rkt“ attempts to
create a temporary file in whatever the result of ‘(path-only path)’ is,
or in the current directory.

What file is it trying to compile?

> My guess is that the Guix package has something misconfigured so that
> this compilation directory is set to the wrong place, but what?

The root of this path appears to be ‘collectsdir’, which is set up at
‘configure’ time.  This directory seems to be correct, because it
contains Racket modules.  We would only need to ensure that compilation
does not use this directory by default.

I’m guessing that this is controlled by ‘do-get-compilation-dir+name’ in
‘collects/compiler/compilation-path.rkt’.

Does this make any sense?

--
Ricardo

  reply	other threads:[~2018-05-22 22:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22 13:42 Using Racket's raco on on Guix(SD) Christopher Lemmer Webber
2018-05-22 15:01 ` Ricardo Wurmus [this message]
     [not found]   ` <87h8mzoht9.fsf-aeLSDxfgpabR7s880joybQ@public.gmane.org>
2018-07-27 18:38     ` Christopher Lemmer Webber
     [not found] ` <87d0xn24d9.fsf-oPPOFS2i0wrhBEyLrsoctQ@public.gmane.org>
2018-05-24  6:20   ` Konrad Hinsen
     [not found]     ` <0990d521-934b-069b-3f29-faf8a22a5bd0-97jfqw80gc7k1uMJSBkQmQ@public.gmane.org>
2018-08-11 15:18       ` Christopher Lemmer Webber
2018-08-11 20:23         ` bug#30680: [racket-users] " Timothy Sample
     [not found]           ` <87h8k0d54i.fsf-txiMz1+kQXoAvxtiuMwx3w@public.gmane.org>
2018-08-11 21:55             ` bug#30680: " Christopher Lemmer Webber
2018-08-11 22:05               ` bug#30680: [racket-users] " Nils Gillmann
2018-08-11 23:28                 ` bug#30680: " Christopher Lemmer Webber
2018-08-12  2:03                   ` bug#30680: [racket-users] " Timothy Sample
2018-08-12  9:32                     ` Gábor Boskovits
     [not found]                     ` <871sb4cpeu.fsf-txiMz1+kQXoAvxtiuMwx3w@public.gmane.org>
2018-08-12 15:31                       ` bug#30680: " Christopher Lemmer Webber
2018-08-12 20:44                         ` bug#30680: [racket-users] " Timothy Sample

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=87h8mzoht9.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=clacke@gmail.com \
    --cc=cwebber@dustycloud.org \
    --cc=help-guix@gnu.org \
    --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.
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).