all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Martin H." <maze@strahlungsfrei.de>
To: ludo@gnu.org
Cc: guix-devel@gnu.org
Subject: Re: Small documentation improvements
Date: Mon, 07 Aug 2017 01:37:16 +0200	[thread overview]
Message-ID: <99bf43da33aab2ed64a2938d3e2b2546@strahlungsfrei.de> (raw)
In-Reply-To: <87efsplo0w.fsf@gnu.org>

Am 2017-08-05 23:09, schrieb ludo@gnu.org:
> Hi,
> 
> "Martin H." <maze@strahlungsfrei.de> skribis:
> 
>> I've pulled my hair out because I wasn't able to build any
>> package. Turns out the following line at "Running Guix Before It Is
>> Installed"
>> (https://www.gnu.org/software/guix/manual/html_node/Running-Guix-Before-It-Is-Installed.html#Running-Guix-Before-It-Is-Installed):
>> 
>> $ sudo ./pre-inst-env guix-daemon --build-users-group=guixbuild
>> 
>> should rather be
>> 
>> $ sudo -E ./pre-inst-env guix-daemon --build-users-group=guixbuild
>> 
>> Otherwise the daemon won't have the GUILE_LOAD_PATH set correctly. At
>> least when running this from a user checkout of Guix on a GuixSD
>> system.
> 
> Indeed.  I made this change and added a note to explain.  Thanks!

Actually, it seems this change was totally wrong and broke my system. At 
least that's what happened: I didn't really realize it immediately, but 
after this change and the first successful package compile inside my 
guix checkout I ended up with broken links to libgcc and libstd++. That 
means I couldn't run any command anymore. I had to boot a live cd and 
fix those problems manually the hard way in order to get the system to 
boot again.

The "sudo -E" makes GUILE_LOAD_PATH contain the paths of the development 
guix instance *in addition* to the paths of the system instance (in 
/run/current-system). As far as I understand, that then means two guix 
daemons with different packages sources are partially operating on the 
same store directories. The development checkout should rather only use 
its own store directory, right? Can anyone clear up how it is supposed 
to work?

So the documentation change should probably immediately be reverted.

The reason I tried this change in the first place was that each `guix 
build` call ends up with the following error, when the daemon is not 
started with "sudo -E":

> substitute: ;;; Failed to autoload make-session in (gnutls):
> substitute: ;;; ERROR: missing interface for module (gnutls)
> substitute: Backtrace:
> substitute:            1 (primitive-load 
> "/home/martin/git/guix/scripts/guix")
> substitute: In guix/ui.scm:
> substitute:   1331:12  0 (run-guix-command _ . _)
> substitute:
> substitute: guix/ui.scm:1331:12: In procedure run-guix-command:
> substitute: guix/ui.scm:1331:12: In procedure module-lookup: Unbound 
> variable: make-session
> guix build: error: corrupt input while restoring archive from #<closed: 
> file 1fe3d90>

There probably has to be a different solution to this problem. I found 
recent threads with similar problems, but this seems to be different.


Best
Martin

  reply	other threads:[~2017-08-06 23:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 23:02 Small documentation improvements Martin H.
2017-08-05 21:09 ` Ludovic Courtès
2017-08-06 23:37   ` Martin H. [this message]
2017-08-07 18:19     ` Leo Famulari
2017-08-21 15:29     ` Ludovic Courtès

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=99bf43da33aab2ed64a2938d3e2b2546@strahlungsfrei.de \
    --to=maze@strahlungsfrei.de \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maze+guix@strahlungsfrei.de \
    /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.