From: Mathieu Lirzin <mthl@gnu.org>
To: "Jan Synáček" <jan.synacek@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix-0.11 help2man errors during compilation
Date: Fri, 05 Aug 2016 14:19:54 +0200 [thread overview]
Message-ID: <87h9azjtlh.fsf@gnu.org> (raw)
In-Reply-To: <CACA+5f2WsJ_Jxfnh7WANNjsvWdhKfJ5A2Sh9QO0nJfh2TEkaQA@mail.gmail.com> ("Jan \=\?utf-8\?B\?U3luw6HEjWVrIidz\?\= message of "Fri, 5 Aug 2016 10:10:35 +0200")
Hello,
Jan Synáček <jan.synacek@gmail.com> writes:
> I'm getting strange errors:
>
> ...
> HELP2MAN doc/guix-daemon.1
> help2man: can't get `--help' info from guix-daemon
> Try `--no-discard-stderr' if option outputs to stderr
> WARNING: 'help2man' is missing on your system.
> You should only need it if you modified a dependency of a man page.
> You may want to install the GNU Help2man package:
> <http://www.gnu.org/software/help2man/>
> Makefile:4893: recipe for target 'doc/guix-daemon.1' failed
> make: [doc/guix-daemon.1] Error 127 (ignored)
> ...
>
> help2man *is* present on my system. Later on, more man pages in doc/
> are built just fine.
I need some extra information in order to debug this.
- The config.log file and the Makefile from you build directory
- The output of 'make --version' and 'help2man --version'
Are you building from the Git repository or the release tarball?
When you execute make again does it try to rebuild 'doc/guix-daemon.1'
if yes, does it succeed?
Thanks,
--
Mathieu Lirzin
next prev parent reply other threads:[~2016-08-05 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 8:10 guix-0.11 help2man errors during compilation Jan Synáček
2016-08-05 12:19 ` Mathieu Lirzin [this message]
2016-08-06 2:02 ` Alex Vong
2016-08-06 14:16 ` Mathieu Lirzin
2016-08-08 8:13 ` Alex Vong
2016-08-06 7:31 ` Jan Synáček
2016-08-06 13:23 ` Mathieu Lirzin
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=87h9azjtlh.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=guix-devel@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).