From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel <Guix-devel@gnu.org>,
bug-hurd@gnu.org, Thomas Schwinge <thomas@codesourcery.com>,
Samuel Thibault <samuel.thibault@gnu.org>
Subject: Re: GSoC: Porting Guix to Hurd week 3+4 report.
Date: Thu, 04 Jun 2015 22:48:48 +0200 [thread overview]
Message-ID: <87h9qnqjwv.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzMSb5jTZdV+MWLkkD9xVJ5dGczPdZmPHyG-BQVCyaOJjg@mail.gmail.com> (Manolis Ragkousis's message of "Thu, 4 Jun 2015 00:25:15 +0300")
Manolis Ragkousis <manolis837@gmail.com> skribis:
> Hey Thomas, thank you for looking into this.
>
> On 2 June 2015 at 18:55, Thomas Schwinge <thomas@codesourcery.com> wrote:
>> Shame on me, but I've never actively used/built Guix before. I do know
>> about <https://github.com/Phant0mas/Guix-on-Hurd>, and that there must be
>> a Guix manual existing -- but can you help me get started, please?
>> (Pointers to specific parts of documentation are appreciated, of course.)
>
> So let's start with the easy one. Currently Guix can be used only of top of a
> GNU/Linux system. So with that in mind, clone the repo (the one from savannah
> git://git.savannah.gnu.org/guix.git )
> on one such system and make sure you have the dependencies mentioned at
> <http://www.gnu.org/software/guix/manual/guix.html#Requirements> installed.
Alternately, there’s a really easy way: grab the binary tarball and
follow the steps at <http://www.gnu.org/software/guix/download/> (make
sure to check the ownership of /var and /root after unpacking it; the
extracting the current tarball will incorrectly change the owner.)
From there:
git clone git://git.savannah.gnu.org/guix.git
cd guix
git checkout wip-hurd
guix environment guix
autoreconf && ./configure --localstatedir=/var \
--with-libgcrypt-prefix=/gnu/store/... && make
> After it fails go to /tmp/nix-build-gcc-4.7... and there you can find
> the failed build. Everything will be there.
> As for the the logs, they can be found with "ls -ltr
> /usr/local/var/log/guix/drvs/*/*".
.. or “guix build gcc-4.7 --target=i686-pc-gnu --log-file”.
Ludo’.
next prev parent reply other threads:[~2015-06-04 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 8:13 GSoC: Porting Guix to Hurd week 3+4 report Manolis Ragkousis
2015-05-31 20:22 ` Ludovic Courtès
2015-06-02 14:06 ` Manolis Ragkousis
2015-06-02 15:55 ` Thomas Schwinge
2015-06-03 21:25 ` Manolis Ragkousis
2015-06-04 20:48 ` Ludovic Courtès [this message]
2015-06-07 20:55 ` Thomas Schwinge
2015-06-08 11:43 ` Manolis Ragkousis
2015-06-08 12:59 ` Ludovic Courtès
2015-06-08 13:12 ` Manolis Ragkousis
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=87h9qnqjwv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=Guix-devel@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=manolis837@gmail.com \
--cc=samuel.thibault@gnu.org \
--cc=thomas@codesourcery.com \
/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.