From: Jani Nikula <jani.nikula@linux.intel.com>
To: bernhard+linux-doc@lsmod.de,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-doc@vger.kernel.org
Cc: "Bernhard M. Wiedemann" <bwiedemann@suse.de>
Subject: Re: [PATCH] docs: Build kernel docs deterministically
Date: Thu, 05 Sep 2024 15:04:21 +0300 [thread overview]
Message-ID: <878qw6qpbu.fsf@intel.com> (raw)
In-Reply-To: <20240905113531.65375-1-bernhard+linux-doc@lsmod.de>
On Thu, 05 Sep 2024, bernhard+linux-doc@lsmod.de wrote:
> From: "Bernhard M. Wiedemann" <bwiedemann@suse.de>
>
> Because we want reproducible builds
> and https://github.com/sphinx-doc/sphinx/issues/6714
> did not receive any love from Sphinx devs in five years,
> let's disable parallel doc builds until that Sphinx issue is fixed.
You mention in [1] that this is likely a duplicate of [2] i.e. multiple
Sphinx instances running in parallel and racing in doctree access.
In kernel, does the issue then boil down to:
htmldocs:
@$(srctree)/scripts/sphinx-pre-install --version-check
@+$(foreach var,$(SPHINXDIRS),$(call loop_cmd,sphinx,html,$(var),,$(var)))
i.e. multiple Sphinx invocations instead of just one?
Broken record, I still think we should axe the Makefile hacks out of the
Sphinx build altogether, and let Sphinx handle everything, via
extensions if necessary.
BR,
Jani.
[1] https://github.com/sphinx-doc/sphinx/issues/6714#issuecomment-1848975385
[2] https://github.com/sphinx-doc/sphinx/issues/2946
>
> This patch was done while working on reproducible builds for openSUSE,
> sponsored by the NLnet NGI0 fund.
>
> Signed-off-by: Bernhard M. Wiedemann <bwiedemann@suse.de>
> ---
> Documentation/sphinx/parallel-wrapper.sh | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/sphinx/parallel-wrapper.sh b/Documentation/sphinx/parallel-wrapper.sh
> index e54c44ce117d..cb93626bd86e 100644
> --- a/Documentation/sphinx/parallel-wrapper.sh
> +++ b/Documentation/sphinx/parallel-wrapper.sh
> @@ -10,6 +10,9 @@ sphinx="$1"
> shift || true
>
> parallel="$PARALLELISM"
> +# Because of issues in Sphinx(https://github.com/sphinx-doc/sphinx/issues/6714)
> +# we disable parallel doc generation to get deterministic build results
> +parallel=1
> if [ -z "$parallel" ] ; then
> # If no parallelism is specified at the top-level make, then
> # fall back to the expected "-jauto" mode that the "htmldocs"
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-05 12:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 11:35 [PATCH] docs: Build kernel docs deterministically bernhard+linux-doc
2024-09-05 12:04 ` Jani Nikula [this message]
2024-09-05 12:20 ` Jani Nikula
2024-09-05 13:29 ` Vegard Nossum
2024-09-05 14:08 ` Jani Nikula
2024-09-05 14:50 ` Vegard Nossum
2024-09-05 12:57 ` Bernhard M. Wiedemann
2024-09-05 13:07 ` Jani Nikula
2024-09-05 18:01 ` Jonathan Corbet
2024-09-05 18:38 ` Jani Nikula
2024-09-05 19:19 ` Jani Nikula
2024-09-06 13:43 ` Bernhard M. Wiedemann
2024-09-06 9:11 ` Vegard Nossum
2024-09-06 13:56 ` Bernhard M. Wiedemann
2024-09-06 14:53 ` Akira Yokosawa
2024-09-20 7:01 ` [PATCH] docs/zh_TW+zh_CN: Make rst references unique bernhard+linux-doc
2024-09-23 5:36 ` Yanteng Si
2024-10-07 17:23 ` 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=878qw6qpbu.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=bernhard+linux-doc@lsmod.de \
--cc=bwiedemann@suse.de \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).