From: ludo@gnu.org (Ludovic Courtès)
To: "Jan Synáček" <jan.synacek@gmail.com>
Cc: 21974-done@debbugs.gnu.org
Subject: bug#21974: can't build guix without 'makeinfo'
Date: Sun, 22 Nov 2015 11:31:51 +0100 [thread overview]
Message-ID: <87vb8u2ulk.fsf@gnu.org> (raw)
In-Reply-To: <CACA+5f3jiy4fz_buBZKwNmyjdeY3Pv-kjK0c+VSRhe_jebvyUQ@mail.gmail.com> ("Jan \=\?utf-8\?B\?U3luw6HEjWVrIidz\?\= message of "Sat, 21 Nov 2015 21:48:10 +0100")
Jan Synáček <jan.synacek@gmail.com> skribis:
> On Sat, Nov 21, 2015 at 9:40 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>> Jan Synáček <jan.synacek@gmail.com> skribis:
>>
>>> The build fails with an error if the 'makeinfo' binary is missing on
>>> the system. The configure script should check for 'makeinfo' and fail
>>> if not found (or maybe warn that the docs won't be built?).
>>
>> ‘makeinfo’ is necessary when building from a checkout or otherwise
>> modifying the manual, but it’s not necessary when building from a
>> tarball. See
>> <https://www.gnu.org/software/guix/manual/html_node/Building-from-Git.html>.
>>
>> Can you confirm you were building from a checkout?
>
> Yes, I was building from a checkout.
OK.
> Maybe it would make sense to make it optional, as 'help2man' is? I was
> only trying to test the latest version of guix and wasn't really
> interested in the documentation changes.
I think it cannot be made more optional than it currently is.
‘MAKEINFO’ is currently defined as:
MAKEINFO = ${SHELL} …/build-aux/missing makeinfo
meaning that you get a warning when ‘makeinfo’ is missing.
Regardless, I would recommend the following to set up a development
environment for Guix:
guix environment guix
I realize this wasn’t documented, so I’ve added it to “Building from
Git.”
Thanks,
Ludo’.
prev parent reply other threads:[~2015-11-22 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 20:19 bug#21974: can't build guix without 'makeinfo' Jan Synáček
2015-11-21 20:40 ` Ludovic Courtès
2015-11-21 20:48 ` Jan Synáček
2015-11-22 10:31 ` Ludovic Courtès [this message]
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=87vb8u2ulk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=21974-done@debbugs.gnu.org \
--cc=jan.synacek@gmail.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).