From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Fis Trivial <ybbs.daans@hotmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Errors encountered in building guix from source.
Date: Sat, 20 Jan 2018 21:45:50 +0100 [thread overview]
Message-ID: <20180120204550.GA13574@thebird.nl> (raw)
In-Reply-To: <MWHPR16MB0063863252112FF78DAF338B92EE0@MWHPR16MB0063.namprd16.prod.outlook.com>
On Sat, Jan 20, 2018 at 08:16:04PM +0000, Fis Trivial wrote:
> I am currently running guix on top of Fedora 26. This is a mix of several
> problems, and possibly contains bugs in guix, I am not sure if I have done
> anything wrong. So I will try to describe them in order. If you believe I
> should make separate threads or fill a bug report, just tell me to.
>
>
> I tried to build guix from git repo according to this menu:
> https://www.gnu.org/software/guix/manual/guix.html#Building-from-Git
>
> * Do as the menu said
> So I ran the following command in sequence:
> $ guix environment guix --ad-hoc help2man git strace
> $ ./bootstrap
> $ ./configure --localstatedir=/var
This looks inadequate to me. Try my
https://gitlab.com/pjotrp/guix-notes/blob/master/INSTALL.org
See building guix from guix - the bullet proof way. It builds Guix
inside Guix tooling - no leakage.
Pj.
next prev parent reply other threads:[~2018-01-20 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 20:16 Errors encountered in building guix from source Fis Trivial
2018-01-20 20:45 ` Pjotr Prins [this message]
2018-01-21 9:13 ` Fis Trivial
2018-01-21 10:50 ` Pjotr Prins
2018-01-24 14:32 ` Ludovic Courtès
2018-01-25 15:12 ` Oleg Pykhalov
2018-01-25 20:58 ` Fis Trivial
2018-01-26 15:25 ` Oleg Pykhalov
2018-01-27 15:12 ` Fis Trivial
2018-01-29 19:20 ` Oleg Pykhalov
2018-01-29 22:35 ` Fis Trivial
2018-01-28 3:16 ` Chris Marusich
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=20180120204550.GA13574@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=ybbs.daans@hotmail.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).