unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jeff Mickey <j@codemac.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Running guix on nixos
Date: Sun, 24 Jan 2016 13:58:51 -0800	[thread overview]
Message-ID: <878u3ey6zo.fsf@nevada.int.iggy.bz> (raw)
In-Reply-To: <87h9i4uimh.fsf@gnu.org>

* Ludovic Courtès <ludo@gnu.org> [2016-01-23 12:48]:
> It would be interesting (on an intellectual level ;-)) to find out what
> piece of libstdc++’s build system is responsible for choosing lib/
> vs. lib64/ and what makes it choose something different.  I’m guessing
> there’s necessarily an impurity in the build environment that explains
> this.

Never figured this out, seems it was the chroot issue, and maybe not
running garbage collection when I thought I was. Sorry I don't have any
logs.

> Yes, you would be using two completely separate distros anyway.  The
> advantages of using a single store, though, is that you would get
> deduplication across the two distros, and running ‘guix gc’ or
> ‘nix-collect-garbage’ would affect the whole store.

I successfully got both the guix-daemon and the nix-daemon running on
the same machine through nix's configuration syntax.

Unfortunately, there is something wrong with how it uses acl, as it
warns me every time and then re-builds the world. Just installing guix
this way as it stands took 10+ hours of compute on an 8 core xeon with
32 gigs of ram.

So.. I need to figure out the substitutes issue (which mark_weaver on
irc rightly pointed out requires the second daemon in /gnu to have all
the package derivations match), and I think maybe my sysconfdir gets set
incorrectly.

Now if only I had fully free hardware so I could hack on guixsd more
easily.. but other than that, I'm very close! Redankon!

  //  codemac

  reply	other threads:[~2016-01-24 21:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 21:56 Running guix on nixos Jeff Mickey
2016-01-21  9:02 ` Ludovic Courtès
2016-01-21 22:24   ` Jeff Mickey
2016-01-22 12:57     ` Ludovic Courtès
2016-01-22 21:43       ` Jeff Mickey
2016-01-23 20:48         ` Ludovic Courtès
2016-01-24 21:58           ` Jeff Mickey [this message]
2016-01-25  8:06             ` Ludovic Courtès
2016-01-25 19:29               ` Jeff Mickey
2016-01-25 21:00                 ` Leo Famulari
2016-01-26 14:09                 ` Ludovic Courtès
2016-01-22 18:45     ` Jeff Mickey

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=878u3ey6zo.fsf@nevada.int.iggy.bz \
    --to=j@codemac.net \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    /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).