public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-3894] sphinx: stop using parallel mode Date: Fri, 11 Nov 2022 12:34:45 +0000 (GMT) [thread overview] Message-ID: <20221111123445.3D4AE3858C00@sourceware.org> (raw) https://gcc.gnu.org/g:08fd14f9589b6e0e3155ba728a5e7031b9250f91 commit r13-3894-g08fd14f9589b6e0e3155ba728a5e7031b9250f91 Author: Martin Liska <mliska@suse.cz> Date: Fri Nov 11 13:32:01 2022 +0100 sphinx: stop using parallel mode Noticed that the documentation build can stuck on a machine with many cores (160) and I identified a real sphinx problem: https://github.com/sphinx-doc/sphinx/issues/10969 Note the parallel can help just for some manuals and it is not critical for us. ChangeLog: * doc/Makefile: Disable -j auto. Diff: --- doc/Makefile | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/Makefile b/doc/Makefile index 9e305a8e7da..e08a43ecf2d 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -2,7 +2,11 @@ # # You can set these variables from the command line. -SPHINXOPTS ?= -j auto -q + +# Disable parallel reading as it can be very slow on a machine with CPUs: +# https://github.com/sphinx-doc/sphinx/issues/10969 + +SPHINXOPTS ?= -q SPHINXBUILD ?= sphinx-build PAPER ?= SOURCEDIR = .
reply other threads:[~2022-11-11 12:34 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221111123445.3D4AE3858C00@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).