all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Claes Wallin (韋嘉誠)" <gnu@clacke.user.lysator.liu.se>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Compile guix from git?
Date: Thu, 25 Jun 2015 11:25:25 +0200	[thread overview]
Message-ID: <87si9gm96i.fsf@gnu.org> (raw)
In-Reply-To: <CAGv_=BpSSq4yQ8rC2ABPFts55LmuiQTgDS5ZvHDros-eoB-LVA@mail.gmail.com> ("Claes Wallin \=\?utf-8\?B\?KOmfi+WYieiqoCkiJ3M\=\?\= message of "Wed, 24 Jun 2015 22:48:49 +0200")

"Claes Wallin (韋嘉誠)" <gnu@clacke.user.lysator.liu.se> skribis:

> How do people compile guix directly from git source? I've been
> searching around in HACKING and manual.html#Contributing and other
> places, the internet in general, and haven't been able to find any
> instructions.
>
> It ought to be:
>
> 1. Get dependencies manually or with 'guix environment guix'.
> 2. aclocal
> 3. automake, maybe automake -a
> 4. autoconf
> 5. configure --sharedstatedir=/var --with-libgcrypt-prefix=wherever
> 6. make

Replace #2, #3, and #4 with just “autoreconf -vfi”.

For #5, you probably mean --localstatedir, not --sharedstatedir.

> But #3 fails. nix/config.h.in is missing, maybe other things too but
> that's where it halts.

Don’t worry, ‘autoreconf’ will do the right thing.  :-)

Alternately, you can also do:

  guix build guix --with-source=/path/to/guix

where the last component of /path/to/guix is literally ‘guix’, and where
/path/to/guix contains a possibly pristine checkout.  But of course,
that command builds from scratch, which may not be what you want.

HTH!

Ludo’.

  parent reply	other threads:[~2015-06-25  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 20:48 Compile guix from git? Claes Wallin (韋嘉誠)
2015-06-25  9:05 ` Mathieu Lirzin
2015-06-25  9:15   ` Claes Wallin (韋嘉誠)
2015-06-25 11:37     ` Ludovic Courtès
2015-06-25  9:25 ` Ludovic Courtès [this message]
2015-06-25  9:38   ` Claes Wallin (韋嘉誠)

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=87si9gm96i.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=gnu@clacke.user.lysator.liu.se \
    --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.