From: Jonathan Corbet <corbet@lwn.net>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux-kernel@vger.kernel.org, Jani Nikula <jani.nikula@intel.com>
Subject: Re: Makefile.sphinx:17: The 'sphinx-build' command was not found
Date: Fri, 29 Jul 2016 07:48:26 -0600 [thread overview]
Message-ID: <20160729074826.27adb9fd@lwn.net> (raw)
In-Reply-To: <alpine.DEB.2.20.12.1607281438520.8973@trent.utfs.org>
On Thu, 28 Jul 2016 15:05:07 -0700 (PDT)
Christian Kujau <lists@nerdbynature.de> wrote:
> Indeed, I don't have "sphinx-build" installed (nor do I want to build
> documentation), running "make SPHINXBUILD=/bin/true help" makes the
> warning go away. Is there a way to omit the warning when
> running "make help"? E.g. by not including Documentation/Makefile.sphinx
> for that target?
That seems like a reasonable request, we'll make it happen.
Thanks,
jon
next prev parent reply other threads:[~2016-07-29 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 22:05 Makefile.sphinx:17: The 'sphinx-build' command was not found Christian Kujau
2016-07-29 13:48 ` Jonathan Corbet [this message]
2016-08-01 9:34 ` Jani Nikula
2016-08-01 9:37 ` [PATCH] Documentation/sphinx: do not warn about missing tools in 'make help' Jani Nikula
2016-08-03 21:42 ` Jonathan Corbet
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=20160729074826.27adb9fd@lwn.net \
--to=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox