From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: configure: check if xmlto exists at configure time
Date: Wed, 11 Apr 2018 16:41:27 +0800 [thread overview]
Message-ID: <272e4be1-7b82-dde4-9623-ca7fbf8051de@gmx.com> (raw)
In-Reply-To: <29b3fdcb-afbc-b3b3-41c3-825f778ccecd@jp.fujitsu.com>
On 2018年04月11日 16:29, Misono Tomohiro wrote:
> AC_PATH_PROG won't fail even if it fails to find command path.
> xmlto is required for document build and we should report error
> if it doesn't exist at configure time.
>
> Signed-off-by: Tomohiro Misono <misono.tomohiro@jp.fujitsu.com>
Looks good.
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> configure.ac | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/configure.ac b/configure.ac
> index af13a959..a4c98b31 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -93,7 +93,11 @@ AC_SUBST([DISABLE_DOCUMENTATION])
> dnl detect tools to build documentation
> ASCIIDOC_TOOL="none"
> if test "x$enable_documentation" = xyes; then
> - AC_PATH_PROG([XMLTO], [xmlto], [xmlto])
> + AC_PATH_PROG([XMLTO], [xmlto])
> + if test -z "$XMLTO"; then
> + AC_MSG_ERROR([cannot find xmlto, cannot build documentation])
> + fi
> +
> AC_PATH_PROG([GZIP], [gzip], [gzip])
> AC_PATH_PROG([MV], [mv], [mv])
> AC_PROG_SED
>
next prev parent reply other threads:[~2018-04-11 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 8:29 [PATCH] btrfs-progs: configure: check if xmlto exists at configure time Misono Tomohiro
2018-04-11 8:41 ` Qu Wenruo [this message]
2018-04-11 13:16 ` David Sterba
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=272e4be1-7b82-dde4-9623-ca7fbf8051de@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=misono.tomohiro@jp.fujitsu.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.
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.