From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Markus Heiser <markus.heiser@darmarit.de>
Subject: Re: Documentation/media/uapi/cec/ sporadically unnecessarily rebuilding
Date: Mon, 24 Oct 2016 07:42:56 -0200 [thread overview]
Message-ID: <20161024074256.3a2eb697@vento.lan> (raw)
In-Reply-To: <871sz6p17k.fsf@intel.com>
Em Mon, 24 Oct 2016 12:04:31 +0300
Jani Nikula <jani.nikula@intel.com> escreveu:
> I think I saw some of this in the past [1], but then couldn't reproduce
> it after all. Now I'm seeing it again. Sporadically
> Documentation/media/uapi/cec/ gets rebuilt on successive runs of make
> htmldocs, even when nothing has changed.
>
> Output of 'make SPHINXOPTS="-v -v" htmldocs' attached for both cases.
>
> Using Sphinx (sphinx-build) 1.4.6
I notice some erratic behavior like that too, when I was writing the
admin-guide and process books... Sometimes, Sphinx decide to rebuild
everything (media, gpu, etc) without a good reason. Also, sometimes,
I was forced to run make cleandocs, as just touching at an rst file
or at a file parsed by kernel-doc is not enough.
The only safe way to be sure that the documentation will be OK and
won't take too long to build is to use:
make cleandocs; make DOCBOOKS="" SPHINXDIRS="admin-guide process" SPHINXOPTS="-j11" htmldocs
It will generate warnings, though, due to the cross-references between
admin-guide and process books. Due to that, after testing for individual
changes, I run:
make cleandocs; make DOCBOOKS="" SPHINXOPTS="-j11" htmldocs
To check those references.
I didn't see any improvement for that on Sphinx 1.4.7 or 1.4.8.
Thanks,
Mauro
next prev parent reply other threads:[~2016-10-24 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 9:04 Documentation/media/uapi/cec/ sporadically unnecessarily rebuilding Jani Nikula
2016-10-24 9:42 ` Mauro Carvalho Chehab [this message]
2016-10-27 14:48 ` Markus Heiser
2016-10-27 14:52 ` Jani Nikula
2016-10-27 20:53 ` Markus Heiser
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=20161024074256.3a2eb697@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=hverkuil@xs4all.nl \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarit.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 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.