all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Building GUIX
Date: Thu, 8 May 2014 15:02:40 +0200	[thread overview]
Message-ID: <20140508130240.GA13827@thebird.nl> (raw)
In-Reply-To: <20140508125254.GB7094@debian>

On Thu, May 08, 2014 at 02:52:54PM +0200, Andreas Enge wrote:
> On Thu, May 08, 2014 at 02:32:00PM +0200, Pjotr Prins wrote:
> > I am not having much luck installing GUIX because of the long list of
> > version specific dependencies. The best route, so far, is installing
> > Nix 1.7 first and then try to bootstrap using those tools. Now I have
> 
> What do you mean by "version specific dependencies"? I have no problems
> on my debian stable, which certainly does not have the newest version of
> anything...

On a fresh Debian I could make it work. On an aging centos it is too
hard. But that is beside the point, I am almost there with Nixpkgs
available. My question is How do I tell 'configure' what guile to use? 

Pj.

  reply	other threads:[~2014-05-08 13:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 12:32 Building GUIX Pjotr Prins
2014-05-08 12:52 ` Andreas Enge
2014-05-08 13:02   ` Pjotr Prins [this message]
2014-05-08 13:30 ` Pjotr Prins
2014-05-08 13:42 ` Cyril Roelandt
2014-05-08 14:56   ` Pjotr Prins
2014-05-08 15:08     ` Pjotr Prins
2014-05-08 19:53       ` Pjotr Prins
2014-05-08 21:08         ` Ludovic Courtès
2014-05-08 16:42 ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2014-05-09 10:57 Building Guix Pjotr Prins
2014-05-09 12:33 ` Ludovic Courtès
2014-05-09 18:51 ` Pjotr Prins
2014-05-09 20:22   ` Ludovic Courtès
2014-05-10  6:46     ` Pjotr Prins
2014-05-10 13:06       ` 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=20140508130240.GA13827@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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.
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.