Generating html linux documentation with sphinx
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I am trying to generate linux documentation from the Documentation folder. This link suggests running make htmldocs in the Documentation folder, but whenever I try that, I get this error:
Reading makefiles...
Updating goal targets....
File 'htmldocs' does not exist.
Must remake target 'htmldocs'.
make: *** empty variable name. Stop.
Makefile:68: recipe for target 'htmldocs' failed
make: *** [htmldocs] Error 2
Any ideas how I can build the documentation?
linux-kernel python
asked Apr 11 at 8:38
sarpu
2115
add a comment |Â
up vote
1
down vote
favorite
I am trying to generate linux documentation from the Documentation folder. This link suggests running make htmldocs in the Documentation folder, but whenever I try that, I get this error:
Reading makefiles...
Updating goal targets....
File 'htmldocs' does not exist.
Must remake target 'htmldocs'.
make: *** empty variable name. Stop.
Makefile:68: recipe for target 'htmldocs' failed
make: *** [htmldocs] Error 2
Any ideas how I can build the documentation?
linux-kernel python
asked Apr 11 at 8:38
sarpu
2115
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am trying to generate linux documentation from the Documentation folder. This link suggests running make htmldocs in the Documentation folder, but whenever I try that, I get this error:
Reading makefiles...
Updating goal targets....
File 'htmldocs' does not exist.
Must remake target 'htmldocs'.
make: *** empty variable name. Stop.
Makefile:68: recipe for target 'htmldocs' failed
make: *** [htmldocs] Error 2
Any ideas how I can build the documentation?
linux-kernel python
asked Apr 11 at 8:38
sarpu
2115
I am trying to generate linux documentation from the Documentation folder. This link suggests running make htmldocs in the Documentation folder, but whenever I try that, I get this error:
Reading makefiles...
Updating goal targets....
File 'htmldocs' does not exist.
Must remake target 'htmldocs'.
make: *** empty variable name. Stop.
Makefile:68: recipe for target 'htmldocs' failed
make: *** [htmldocs] Error 2
Any ideas how I can build the documentation?
linux-kernel python
asked Apr 11 at 8:38
sarpu
2115
asked Apr 11 at 8:38
sarpu
2115
asked Apr 11 at 8:38
sarpu
2115
asked Apr 11 at 8:38
sarpu
2115
2115
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
You shouldn’t run make htmldocs inside the Documentation directory; run it from the base kernel directory instead.
(This is true for the vast majority of kernel build commands: unless you specifically know otherwise, they should always be run from the base kernel directory, even when building sub-directories.)
answered Apr 11 at 8:44
Stephen Kitt
140k22305365
Ok, this time I get this errorreST markup error: /home/sarp/projects/eudyptula/linux/Documentation/driver-api/usb/typec.rst:215: (SEVERE/4) Unexpected section title or transition.@StephenKitt. Any advice?
– sarpu
Apr 11 at 9:34
1
Hmm, the file was broken by this commit; you could revert it, the previous version of the.rstfile has valid syntax.
– Stephen Kitt
Apr 11 at 10:08
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
You shouldn’t run make htmldocs inside the Documentation directory; run it from the base kernel directory instead.
(This is true for the vast majority of kernel build commands: unless you specifically know otherwise, they should always be run from the base kernel directory, even when building sub-directories.)
answered Apr 11 at 8:44
Stephen Kitt
140k22305365
Ok, this time I get this errorreST markup error: /home/sarp/projects/eudyptula/linux/Documentation/driver-api/usb/typec.rst:215: (SEVERE/4) Unexpected section title or transition.@StephenKitt. Any advice?
– sarpu
Apr 11 at 9:34
1
Hmm, the file was broken by this commit; you could revert it, the previous version of the.rstfile has valid syntax.
– Stephen Kitt
Apr 11 at 10:08
add a comment |Â
up vote
2
down vote
accepted
You shouldn’t run make htmldocs inside the Documentation directory; run it from the base kernel directory instead.
(This is true for the vast majority of kernel build commands: unless you specifically know otherwise, they should always be run from the base kernel directory, even when building sub-directories.)
answered Apr 11 at 8:44
Stephen Kitt
140k22305365
Ok, this time I get this errorreST markup error: /home/sarp/projects/eudyptula/linux/Documentation/driver-api/usb/typec.rst:215: (SEVERE/4) Unexpected section title or transition.@StephenKitt. Any advice?
– sarpu
Apr 11 at 9:34
1
Hmm, the file was broken by this commit; you could revert it, the previous version of the.rstfile has valid syntax.
– Stephen Kitt
Apr 11 at 10:08
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
You shouldn’t run make htmldocs inside the Documentation directory; run it from the base kernel directory instead.
(This is true for the vast majority of kernel build commands: unless you specifically know otherwise, they should always be run from the base kernel directory, even when building sub-directories.)
answered Apr 11 at 8:44
Stephen Kitt
140k22305365
You shouldn’t run make htmldocs inside the Documentation directory; run it from the base kernel directory instead.
(This is true for the vast majority of kernel build commands: unless you specifically know otherwise, they should always be run from the base kernel directory, even when building sub-directories.)
answered Apr 11 at 8:44
Stephen Kitt
140k22305365
answered Apr 11 at 8:44
Stephen Kitt
140k22305365
answered Apr 11 at 8:44
Stephen Kitt
140k22305365
answered Apr 11 at 8:44
Stephen Kitt
140k22305365
140k22305365
Ok, this time I get this errorreST markup error: /home/sarp/projects/eudyptula/linux/Documentation/driver-api/usb/typec.rst:215: (SEVERE/4) Unexpected section title or transition.@StephenKitt. Any advice?
– sarpu
Apr 11 at 9:34
1
Hmm, the file was broken by this commit; you could revert it, the previous version of the.rstfile has valid syntax.
– Stephen Kitt
Apr 11 at 10:08
add a comment |Â
Ok, this time I get this errorreST markup error: /home/sarp/projects/eudyptula/linux/Documentation/driver-api/usb/typec.rst:215: (SEVERE/4) Unexpected section title or transition.@StephenKitt. Any advice?
– sarpu
Apr 11 at 9:34
1
Hmm, the file was broken by this commit; you could revert it, the previous version of the.rstfile has valid syntax.
– Stephen Kitt
Apr 11 at 10:08
Ok, this time I get this error
reST markup error: /home/sarp/projects/eudyptula/linux/Documentation/driver-api/usb/typec.rst:215: (SEVERE/4) Unexpected section title or transition. @StephenKitt. Any advice?– sarpu
Apr 11 at 9:34
Ok, this time I get this error
reST markup error: /home/sarp/projects/eudyptula/linux/Documentation/driver-api/usb/typec.rst:215: (SEVERE/4) Unexpected section title or transition. @StephenKitt. Any advice?– sarpu
Apr 11 at 9:34
1
1
Hmm, the file was broken by this commit; you could revert it, the previous version of the
.rst file has valid syntax.– Stephen Kitt
Apr 11 at 10:08
Hmm, the file was broken by this commit; you could revert it, the previous version of the
.rst file has valid syntax.– Stephen Kitt
Apr 11 at 10:08
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f436953%2fgenerating-html-linux-documentation-with-sphinx%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
