From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
linux-next@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
broonie@kernel.org
Subject: Re: docs build problems
Date: Wed, 15 Oct 2025 15:15:37 -0600 [thread overview]
Message-ID: <87sefj7tom.fsf@trenco.lwn.net> (raw)
In-Reply-To: <c9e9134c-97a2-405a-918d-41aafdd92fa1@infradead.org>
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...?
jon
next prev parent reply other threads:[~2025-10-15 21:15 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 [this message]
2025-10-15 21:16 ` Randy Dunlap
2025-10-15 21:44 ` Mauro Carvalho Chehab
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=87sefj7tom.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=broonie@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab+huawei@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.