From: Akira Yokosawa <akiyks@gmail.com>
To: rdunlap@infradead.org
Cc: broonie@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
Akira Yokosawa <akiyks@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: linux-next: Tree for Sep 19 (make htmldocs problem)
Date: Sun, 21 Sep 2025 17:43:38 +0900 [thread overview]
Message-ID: <54d1f3b1-ba8c-458b-92d6-9d8880952e06@gmail.com> (raw)
In-Reply-To: <883df949-0281-4a39-8745-bcdcce3a5594@infradead.org>
Hi Randy,
On Sat, 20 Sep 2025 17:17:56 -0700, Randy Dunlap wrote:
> Hi,
>
> On 9/19/25 8:05 AM, Mark Brown wrote:
>
> With today's linux-next, when I do 'make O=DOC1 htmldocs', I get:
>
> make[1]: Entering directory '/home/rdunlap/lnx/repo/linux-next/DOC1'
> ../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
> ELF
> SyntaxError: source code cannot contain null bytes
> make[1]: Leaving directory '/home/rdunlap/lnx/repo/linux-next/DOC1'
>
> where the "ELF" line contains some binary bytes that are not shown
> via copy/paste. Here they are in hex in case that might help:
>
> 7f 45 4c 46 02 01 01 0a .ELF....
>
Hmm, my /usr/bin/sphinx-build (under Ubuntu 24.04) is a python script.
Running "file /usr/bin/sphinx-build" says:
/usr/bin/sphinx-build: Python script, ASCII text executable
Randy, how did you install the sphinx-build? And which distro are you
on?
>
> I don't see what is causing this, so I am using the previous day's
> linux-next for Documentation testing etc...
Another question ...
Does going back to a past linux-next make sphinx-build work again?
If that's the case ..., I'm not sure, but it might be related to
Mauro's sphinx-build-wrapper, which is now in docs-next (not in docs-mw
for v6.18 at the moment).
Randy, what happens if you revert the latter part of Mauro's series, namely,
819667bc3ccd ("tools/docs: sphinx-build-wrapper: add a wrapper for sphinx-build")
2e1760999e58 ("docs: parallel-wrapper.sh: remove script")
... up to ...
42180ada39da ("tools/docs: sphinx-build-wrapper: add support to run inside venv")
on top of next-20250919 ?
Regards,
Akira
>
> Any ideas/suggestions appreciated.
>
> --
> ~Randy
>
next prev parent reply other threads:[~2025-09-21 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aM1xVa_SX3_QFU_q@sirena.org.uk>
2025-09-21 0:17 ` linux-next: Tree for Sep 19 (make htmldocs problem) Randy Dunlap
2025-09-21 8:43 ` Akira Yokosawa [this message]
2025-09-21 14:03 ` Jonathan Corbet
2025-09-21 15:59 ` Randy Dunlap
2025-09-21 19:27 ` Jonathan Corbet
2025-09-21 20:32 ` Mauro Carvalho Chehab
2025-09-21 20:44 ` Jonathan Corbet
2025-09-21 21:43 ` Mauro Carvalho Chehab
2025-09-21 21:56 ` Jonathan Corbet
2025-09-21 22:06 ` Mauro Carvalho Chehab
2025-09-21 21:10 ` 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=54d1f3b1-ba8c-458b-92d6-9d8880952e06@gmail.com \
--to=akiyks@gmail.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox