From: Randy Dunlap <rdunlap@infradead•org>
To: Jonathan Corbet <corbet@lwn•net>,
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 14:16:56 -0700 [thread overview]
Message-ID: <22e7918a-58f6-4451-a489-7aec4ab8d765@infradead.org> (raw)
In-Reply-To: <87sefj7tom.fsf@trenco.lwn.net>
On 10/15/25 2:15 PM, Jonathan Corbet wrote:
> 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
and sphinx-build-wrapper fix also.
--
~Randy
next prev parent reply other threads:[~2025-10-15 21:16 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 [this message]
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=22e7918a-58f6-4451-a489-7aec4ab8d765@infradead.org \
--to=rdunlap@infradead$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab+huawei@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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