Generating html linux documentation with sphinx

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite
1












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




share|improve this question
























    up vote
    1
    down vote

    favorite
    1












    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




    share|improve this question






















      up vote
      1
      down vote

      favorite
      1









      up vote
      1
      down vote

      favorite
      1






      1





      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




      share|improve this question












      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





      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 11 at 8:38









      sarpu

      2115




      2115




















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






          share|improve this answer




















          • 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




            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










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          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

















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






          share|improve this answer




















          • 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




            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














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






          share|improve this answer




















          • 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




            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












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






          share|improve this answer












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







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 11 at 8:44









          Stephen Kitt

          140k22305365




          140k22305365











          • 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




            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
















          • 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




            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















          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












           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          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
































































          -

          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
          Read more

          Displaying single band from multi-band raster using QGIS

          Image
          Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
          Read more

          How many registers does an x86_64 CPU actually have?

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
          Read more