From: grunpferd at netscape.net <grunpferd@netscape.net>
To: buildroot@busybox.net
Subject: [Buildroot] Failing gst1-validate-1.12.2 build, documentation not necessary!
Date: Wed, 9 Aug 2017 08:02:25 -0400 [thread overview]
Message-ID: <15dc6dfd7fa-50f8-9d22@webprd-a03.mail.aol.com> (raw)
In-Reply-To: <trinity-adc229dc-8010-433a-83e5-915ef6083410-1502267868449@3capp-gmx-bs26>
G'day Peter,
Gave your patch a test and works as expected.
Thanks muchly!
It does appear there was no sphinx documentation system installed with python
Did not realise there was even an option.
So this maybe a useful patch for those systems that do not have this utility available.
Not sure how rare a case this is, but it caught me out.
Thanking you,
Ross
> The problem seems you are one of the rare people who have a (non functional) sphinx documentation
> system installed on the build host....
>
> Mind to try the following (untested) patch:
>
> diff --git a/package/gstreamer1/gst1-validate/gst1-validate.mk b/package/gstreamer1/gst1-validate/gst1-validate.mk
> index be43df4f..5066c277 100644
> --- a/package/gstreamer1/gst1-validate/gst1-validate.mk
> +++ b/package/gstreamer1/gst1-validate/gst1-validate.mk
> @@ -18,4 +18,6 @@ GST1_VALIDATE_DEPENDENCIES = \
> python \
> $(if $(BR2_PACKAGE_CAIRO),cairo)
>
> +GST1_VALIDATE_CONF_ENV = ac_cv_prog_enable_sphinx_doc=no
> +
> $(eval $(autotools-package))
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170809/bf0bf08f/attachment.html>
prev parent reply other threads:[~2017-08-09 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 0:23 [Buildroot] Failing gst1-validate-1.12.2 build, documentation not necessary! grunpferd at netscape.net
2017-08-09 8:37 ` Peter Seiderer
2017-08-09 12:02 ` grunpferd at netscape.net [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=15dc6dfd7fa-50f8-9d22@webprd-a03.mail.aol.com \
--to=grunpferd@netscape.net \
--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