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

[-- Attachment #1: Type: text/plain, Size: 3051 bytes --]

Hi Ricardo,



On Thu, May 2, 2019 at 3:33 PM Ricardo Wurmus <rekado@elephly.net> wrote:

>
> 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.
>
> I understand that this is not an official documentation. I installed guix
through office documentation on my system. It is working fine.


> 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?
>
I need to build guix for non-root location because at several places its
hard to convince to use such system. However, I need several packages which
are not usually available or outdated. The guix projects allows me to do
so. To accomplish that I need truly non-root permission oriented method to
bootstrap and install whatever I deem necessary for my use case.
Unfortunately, I am stuck at Centos6 which uses old
kernel 2.6.32-696.el6.x86_64. I am able to install nix on this system at
non-root location. It works fine but NIx community has decided to use 2.0
which only works on newer kernel. Therefore, I have to now backport several
packages. Making it really hard because lot of packages are broken. Its
manageable but not ideal. Whereas the guix seems to be independent of
kernel (atleast that is my assumption so far).

>
> > ./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)
>

I understand but that is why my personal work machine (running Ubuntu
18.04) is using the 1.0.0 guix not the latest git repo one. Also, I am
boostraping guix/gnu store from tag v1.0.0.

>
> …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.
>

This is the place where I am struggling. I am not sure what more do I need
to do then described in pjotrp notes. I could not find anything specific in
the guix documentation as well to accomplish this.

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.
>

This option is not available as I stated earlier, I do not have the root
permission.

>
> --
> Ricardo
>
> --Rohit

[-- Attachment #2: Type: text/html, Size: 5866 bytes --]

  reply	other threads:[~2019-05-02 21:15 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
2019-05-02 21:14   ` rohit yadav [this message]
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=CAGKZdmbh2XJRWKh22fcHeKE71gVnN1DOogWrLK0agMADnORnAw@mail.gmail.com \
    --to=rohityadav@utexas.edu \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).