From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org
Subject: Re: FAQ
Date: Wed, 10 Jul 2013 15:28:28 +0200 [thread overview]
Message-ID: <87vc4icznn.fsf@gnu.org> (raw)
In-Reply-To: <87ppuq2a7u.fsf@karetnikov.org> (Nikita Karetnikov's message of "Wed, 10 Jul 2013 10:35:49 +0400")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
> +* Building from Git
> +
> +The following errors might appear if you are building from Git. Also,
> +take a look at the [[https://gnu.org/software/guix/manual/guix.html#Installation]["Installation"]] section of the manual and the
> +[[http://git.savannah.gnu.org/cgit/guix.git/tree/README]["Installing Guix from Guix"]] section in 'README'.
Sorry if I wasn’t clear. What I meant is: instead of presenting it as a
trial-and-error approach, I would rather present it as a sequence of
instructions to build from Git.
Something like:
First, make sure Autoconf (>= 2.69), Automake, pkg-config, etc. are
installed. If you get an error like this:
./configure: line 6755: `PKG_CHECK_MODULES(GUILE, guile-2.0 >= 2.0.5)'
then it probably means that pkg-config’s pkg.m4 file was not found by
Automake. Make sure pkg.m4 is available, and possibly add its
directory to the ACLOCAL_PATH environment variable (info "(automake)
Macro Search Path").
Second, run ./bootstrap. Among other things, this will run ‘git
submodule update’. If you get an error like this:
...
Also, when referring to a GNU manual, please show the info command (as I
did above) rather than giving a hyperlink. This will ensure that users
read the right version of the manual.
For the link to README, just use [[./README][README]] (info "(org)
Hyperlinks").
It may look like I’m being picky, and indeed that’s what I am ;-), but I
think it’s important to agree on how to present information.
Thanks for your help!
Ludo’.
next prev parent reply other threads:[~2013-07-10 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51D71116.3080403@BlueT.org>
[not found] ` <87txk8sqc6.fsf@gnu.org>
[not found] ` <51D768DE.90403@BlueT.org>
[not found] ` <878v1jstco.fsf@gnu.org>
[not found] ` <51D9F8EF.5050806@BlueT.org>
[not found] ` <87li5hb71f.fsf@gnu.org>
2013-07-08 17:12 ` [Guix] FTBFS on Ubuntu (12.04) 64bit. Various fatal during install BlueT - Matthew Lien - 練喆明
2013-07-08 20:56 ` Ludovic Courtès
2013-07-08 21:42 ` FAQ Nikita Karetnikov
2013-07-09 11:21 ` FAQ Ludovic Courtès
2013-07-09 19:00 ` FAQ Nikita Karetnikov
2013-07-09 20:03 ` FAQ Ludovic Courtès
2013-07-09 20:26 ` FAQ Nikita Karetnikov
2013-07-09 22:39 ` FAQ Ludovic Courtès
2013-07-10 6:35 ` FAQ Nikita Karetnikov
2013-07-10 13:28 ` Ludovic Courtès [this message]
2013-07-12 20:50 ` FAQ Nikita Karetnikov
2013-07-12 21:41 ` FAQ 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
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=87vc4icznn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=nikita@karetnikov.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 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).