Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] gst1-validate: disable building documentation using sphinx
Date: Wed, 16 Aug 2017 23:15:32 +0200	[thread overview]
Message-ID: <20170816231532.092f66f5@windsurf> (raw)
In-Reply-To: <20170812210610.536-1-arnout@mind.be>

Hello,

On Sat, 12 Aug 2017 23:06:10 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> From: Peter Seiderer <ps.report@gmx.net>
> 
> Fix a build failure in case (a non functional) sphinx documentation
> system is installed on the host (reported [1] and fix tested [2]
> by grunpferd at netscape.net).
> 
> Fixes:
> 
>   sphinx-build -b html -d ./doctrees   . ./html
>   Error: Source directory doesn't contain a conf.py file.
> 
> [1] http://lists.busybox.net/pipermail/buildroot/2017-August/200021.html
> [2] http://lists.busybox.net/pipermail/buildroot/2017-August/200267.html
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> Cc: grunpferd at netscape.net
> [Arnout:
>  - use --disable-sphinx-doc instead of a cv variable
>  - remove the comment, it speaks for itself]
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
>  package/gstreamer1/gst1-validate/gst1-validate.mk | 2 ++
>  1 file changed, 2 insertions(+)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2017-08-16 21:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-12 21:06 [Buildroot] [PATCH v2] gst1-validate: disable building documentation using sphinx Arnout Vandecappelle
2017-08-16 21:15 ` Thomas Petazzoni [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170816231532.092f66f5@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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