docs build problems

docs build problems

[Randy Dunlap]

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\x02\x01\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?

thanks.
-- 
~Randy

Re: docs build problems

[Jonathan Corbet]

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

Re: docs build problems

[Randy Dunlap]

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

Re: docs build problems

[Mauro Carvalho Chehab]

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

Re: docs build problems

[Jonathan Corbet]

Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:

> 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...
>> > 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?

I'll have them around, I think.  I need to figure out why they
disappeared, though; this is a bit weird.

Thanks,

jon

Re: docs build problems

[Jonathan Corbet]

Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:

> 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?

*Sigh*

I forgot to pull the build-script branch back to the desktop machine
once I got back home, so I was missing everything that I applied while
on the road.  That has been rectified, and the needed patches are now in
docs-next.

My apologies for the screwup.

jon

Re: docs build problems

[Mauro Carvalho Chehab]

Em Wed, 15 Oct 2025 15:53:33 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> 
> > 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?  
> 
> *Sigh*
> 
> I forgot to pull the build-script branch back to the desktop machine
> once I got back home, so I was missing everything that I applied while
> on the road.  That has been rectified, and the needed patches are now in
> docs-next.
> 
> My apologies for the screwup.

Heh, that happens ;-)

All patches from my fixes series are there now. 

Looking at my docs pending stuff, the only thing missing is this
series:

	https://lore.kernel.org/linux-doc/cover.1759329363.git.mchehab+huawei@kernel.org/

I double-checked: it applies cleanly on the top of docs-next, as it is
unrelated to build wrapper.

Regards,
Mauro

Re: docs build problems

[Jonathan Corbet]

Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:

> Looking at my docs pending stuff, the only thing missing is this
> series:
>
> 	https://lore.kernel.org/linux-doc/cover.1759329363.git.mchehab+huawei@kernel.org/
>
> I double-checked: it applies cleanly on the top of docs-next, as it is
> unrelated to build wrapper.

In that posting, you said you weren't sure how you wanted it merged, so
I have it just sitting in a folder.  I take it you think I should pick
it up?

jon

Re: docs build problems

[Mauro Carvalho Chehab]

Em Thu, 16 Oct 2025 15:01:04 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> 
> > Looking at my docs pending stuff, the only thing missing is this
> > series:
> >
> > 	https://lore.kernel.org/linux-doc/cover.1759329363.git.mchehab+huawei@kernel.org/
> >
> > I double-checked: it applies cleanly on the top of docs-next, as it is
> > unrelated to build wrapper.  
> 
> In that posting, you said you weren't sure how you wanted it merged, so
> I have it just sitting in a folder.  I take it you think I should pick
> it up?

Maybe the best would be to have it on a separate branch
on the top of 6.18-rc1 and have it merged to both docs and media.

This way, we'll doc build issues and prevent changes on media docs
to break things.

What do you think?

Regards,
Mauro