From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
Mark Brown <broonie@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: linux-next: Tree for Sep 19 (make htmldocs problem)
Date: Sun, 21 Sep 2025 08:03:25 -0600 [thread overview]
Message-ID: <87ldm7c382.fsf@trenco.lwn.net> (raw)
In-Reply-To: <883df949-0281-4a39-8745-bcdcce3a5594@infradead.org>
Mauro, have you seen this ... any ideas ... ? Randy, what can you say
about the environment you're running when you hit this problem?
(It doesn't reproduce here).
jon
Randy Dunlap <rdunlap@infradead.org> writes:
> 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....
>
>
> I don't see what is causing this, so I am using the previous day's
> linux-next for Documentation testing etc...
>
> Any ideas/suggestions appreciated.
>
> --
> ~Randy
next prev parent reply other threads:[~2025-09-21 14:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 15:05 linux-next: Tree for Sep 19 Mark Brown
2025-09-21 0:17 ` linux-next: Tree for Sep 19 (make htmldocs problem) Randy Dunlap
2025-09-21 8:43 ` Akira Yokosawa
2025-09-21 14:03 ` Jonathan Corbet [this message]
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=87ldm7c382.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=broonie@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@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.