From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>
Subject: [PATCH 0/1] fix rustdoc build detection
Date: Mon, 17 Nov 2025 10:12:50 +0100 [thread overview]
Message-ID: <cover.1763370163.git.mchehab+huawei@kernel.org> (raw)
Hi Jon,
For whatever weird reason, at least here sometimes rust config
detection is failing, causing the logic to try building the Kernel
as well, after building the docs.
After some tests, I'm opting to move the rust detection to be inside
the wrapper, at it sounds to me that the building system is not
evaluating well CONFIG_RUST here:
ifeq ($(CONFIG_RUST),y)
RUSTDOC=--rustdoc
endif
Another alternative would be to modify the rustdoc target inside
rust Makefile to make it dependent on htmldocs, but that would require
more work.
Mauro Carvalho Chehab (1):
docs: makefile: move rustdoc check to the build wrapper
Documentation/Makefile | 6 -----
tools/docs/sphinx-build-wrapper | 41 +++++++++++++++++++++++++--------
2 files changed, 32 insertions(+), 15 deletions(-)
--
2.51.1
next reply other threads:[~2025-11-17 9:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 9:12 Mauro Carvalho Chehab [this message]
2025-11-17 9:12 ` [PATCH 1/1] docs: makefile: move rustdoc check to the build wrapper Mauro Carvalho Chehab
2025-11-17 9:20 ` Miguel Ojeda
2025-11-17 11:04 ` Mauro Carvalho Chehab
2025-11-18 16:38 ` Jonathan Corbet
2025-11-18 19:11 ` Mauro Carvalho Chehab
2025-11-18 20:32 ` Mauro Carvalho Chehab
2025-11-18 21:34 ` Miguel Ojeda
2025-11-18 21:40 ` Miguel Ojeda
2025-11-20 20:13 ` Mauro Carvalho Chehab
2025-11-17 9:19 ` [PATCH 0/1] fix rustdoc build detection Miguel Ojeda
2025-11-17 10:48 ` Mauro Carvalho Chehab
2025-11-17 11:22 ` Miguel Ojeda
2025-11-17 11:25 ` Miguel Ojeda
2025-11-17 12:32 ` Mauro Carvalho Chehab
2025-11-18 22:02 ` Miguel Ojeda
2025-11-21 9:40 ` Mauro Carvalho Chehab
2025-11-24 1:51 ` Miguel Ojeda
2025-11-24 8:18 ` Mauro Carvalho Chehab
2025-11-24 8:34 ` Mauro Carvalho Chehab
2025-11-18 23:23 ` Carlos Bilbao
2025-11-21 9:12 ` Mauro Carvalho Chehab
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=cover.1763370163.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ojeda@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).