unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: rohit yadav <rohityadav@utexas.edu>
Cc: guix-devel@gnu.org
Subject: Re: [Non-root Guix]: Unable to build guix
Date: Thu, 02 May 2019 22:33:10 +0200	[thread overview]
Message-ID: <87ftpwwq9l.fsf@elephly.net> (raw)
In-Reply-To: <CAGKZdmb5rcAP8P14HR9jVO5ebSFCvPMi76s2akhsyT3w_5C3Pw@mail.gmail.com>


Hi,

> I am trying to prepare guix for installing at non-root location. I have
> followed the documentation available here:
> https://github.com/pjotrp/guix-notes/blob/master/INSTALL.org#error-in-procedure-scm-error-no-code-for-module-gcrypt-hash

I’d just like to note that this is not official documentation of the
Guix project.  I don’t know if this is still accurate information.

Do you want to build everything from source on your system or do you
prefer to use binaries from the Guix project’s build farms?  Do you have
access to user namespaces / can you use “unshare” for file system
shenanigans?

> ./pre-inst-env guix package -i guix

We don’t recommend using Guix from a git checkout in most cases, because…

> substitute: ERROR: In procedure scm-error:
> substitute: no code for module (gcrypt hash)

…you would need to take care of providing the appropriate Guile
environment all by yourself whereas “guix pull” does all of this for
you.  This error tells you that guile-gcrypt is not available in the
environment in which the daemon runs.

I would also like to suggest an alternative to a root-less installation.
At the HPC cluster where I work we run the guix-daemon as root on a
virtual machine where /gnu/store is a writable NFS share.  Every machine
that uses Guix only needs to mount this share as read-only.

--
Ricardo

  reply	other threads:[~2019-05-02 21:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02 20:15 [Non-root Guix]: Unable to build guix rohit yadav
2019-05-02 20:33 ` Ricardo Wurmus [this message]
2019-05-02 21:14   ` rohit yadav
2019-05-02 21:37     ` Ricardo Wurmus
2019-05-02 22:13       ` rohit yadav
2019-05-02 21:46     ` Ricardo Wurmus
2019-05-02 22:17       ` rohit yadav
2019-05-04  6:14       ` Chris Marusich
2019-05-05  0:39       ` Mark H Weaver
2019-05-05  8:03         ` Ricardo Wurmus
2019-05-02 20:34 ` Ricardo Wurmus
2019-05-02 21:17   ` rohit yadav

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=87ftpwwq9l.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=rohityadav@utexas.edu \
    /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).