From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
linux-next@vger.kernel.org, broonie@kernel.org
Subject: Re: docs build problems
Date: Wed, 15 Oct 2025 18:44:16 -0300 [thread overview]
Message-ID: <20251015184416.4340e8f2@sal.lan> (raw)
In-Reply-To: <87sefj7tom.fsf@trenco.lwn.net>
Em Wed, 15 Oct 2025 15:15:37 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> Randy Dunlap <rdunlap@infradead.org> writes:
>
> > Hi,
> >
> > I am back to having one former error and one former pair of warnings
> > on today's linux-next (20251015):
> >
> > ../Documentation/Makefile:71: warning: overriding recipe for target 'pdfdocs'
> > ../Documentation/Makefile:62: warning: ignoring old recipe for target 'pdfdocs'
> > File "/usr/bin/sphinx-build", line 1
> > \x7fELF.\x01.
> > SyntaxError: source code cannot contain null bytes
> >
> >
> > Did something happen to the docs/docs-next tree or was there some kind
> > of mis-merge problem?
>
> I pulled docs-next forward to -rc1 and merged a few things, but I
> wouldn't expect any of that to create that kind of problem. It seems we
> lost the makefile fix somehow...?
Just did a rebase. Those patches are missing:
e2c3ba36aee2 tools/docs: sphinx-build-wrapper: -q is a boolean, not an integer
0ce66e3f9c8b kernel-doc: output source file name at SEE ALSO
9b34d25a58ae docs: Makefile: use PYTHONPYCACHEPREFIX
d5da902cc340 tools/docs: sphinx-build-wrapper: pdflatex is needed only for pdf
1cad2682b785 docs: Makefile: avoid a warning when using without texlive
f0a4ad647aad tools/docs/sphinx-build-wrapper: allow skipping sphinx-build step
fb4771ad4ff4 docs: Makefile: fix rustdoc detection
ed7faec0095d tools/docs: sphinx-build-wrapper: fix compat with recent Tumbleweed
ab7dde2453af docs: conf.py: get rid of load_config.py
8f421d0c327f scripts: remove sphinx-build-wrapper from scripts/
9a20d16551af tools/docs: sphinx-build-wrapper: handle sphinx-build errors
Want me to re-send them?
Regards,
Mauro
next prev parent reply other threads:[~2025-10-15 21:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 21:06 docs build problems Randy Dunlap
2025-10-15 21:15 ` Jonathan Corbet
2025-10-15 21:16 ` Randy Dunlap
2025-10-15 21:44 ` Mauro Carvalho Chehab [this message]
2025-10-15 21:47 ` Jonathan Corbet
2025-10-15 21:53 ` Jonathan Corbet
2025-10-16 9:23 ` Mauro Carvalho Chehab
2025-10-16 21:01 ` Jonathan Corbet
2025-10-17 8:26 ` 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=20251015184416.4340e8f2@sal.lan \
--to=mchehab+huawei@kernel.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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 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.