Skip to content
Snippets Groups Projects
  1. Feb 01, 2021
  2. Oct 30, 2020
  3. Oct 28, 2020
  4. Apr 20, 2020
  5. Apr 14, 2020
  6. Mar 03, 2020
  7. Feb 19, 2020
  8. Nov 22, 2019
  9. Nov 11, 2019
  10. Oct 10, 2019
  11. Oct 01, 2019
    • Kees Cook's avatar
      docs: Use make invocation's -j argument for parallelism · 29efbb24
      Kees Cook authored
      
      While sphinx 1.7 and later supports "-jauto" for parallelism, this
      effectively ignores the "-j" flag used in the "make" invocation, which
      may cause confusion for build systems. Instead, extract the available
      parallelism from "make"'s job server (since it is not exposed in any
      special variables) and use that for the "sphinx-build" run. Now things
      work correctly for builds where -j is specified at the top-level:
      
      	make -j16 htmldocs
      
      If -j is not specified, continue to fallback to "-jauto" if available.
      
      Signed-off-by: default avatarKees Cook <keescook@chromium.org>
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      29efbb24
  12. Jun 07, 2019
  13. Jun 04, 2019
  14. May 31, 2019
  15. May 30, 2019
    • Mauro Carvalho Chehab's avatar
      docs: by default, build docs a lot faster with Sphinx >= 1.7 · cf08508d
      Mauro Carvalho Chehab authored
      
      Since Sphinx version 1.7, it is possible to use "-jauto" in
      order to speedup documentation builds. On older versions,
      while -j was already supported, one would need to set the
      number of threads manually.
      
      So, if SPHINXOPTS is not provided, add -jauto, in order to
      speed up the build. That makes it *a lot* times faster than
      without -j.
      
      If one really wants to slow things down, it can just use:
      
      	make SPHINXOPTS=-j1 htmldocs
      
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab+samsung@kernel.org>
      [ jc: fixed perl magic to determine sphinx version ]
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      cf08508d
    • Mauro Carvalho Chehab's avatar
      scripts/sphinx-pre-install: always check if version is compatible with build · 9b88ad54
      Mauro Carvalho Chehab authored
      
      Call the script every time a make docs target is selected, on
      a simplified check mode.
      
      With this change, the script will set two vars:
      
      $min_version - obtained from `needs_sphinx` var inside
      	       conf.py (currently, '1.3')
      
      $rec_version - obtained from sphinx/requirements.txt.
      
      With those changes, a target like "make htmldocs" will do:
      
      1) If no sphinx-build/sphinx-build3 is found, it will run
         the script on normal mode as before, checking for all
         system dependencies and providing install hints for the
         needed programs and will abort the build;
      
      2) If no sphinx-build/sphinx-build3 is found, but there is
         a sphinx_${VER}/bin/activate file, and if
         ${VER} >= $min_version (string comparation), it will
         run in full mode, and will recommend to activate the
         virtualenv. If there are multiple virtualenvs, it
         will string sort the versions, recommending the
         highest version and will abort the build;
      
      3) If Sphinx is detected but has a version lower than
         $min_version, it will run in full mode - with will
         recommend creating a virtual env using sphinx/requirements.txt,
         and will abort the build.
      
      4) If Sphinx is detected and version is lower than
         $rec_version, it will run in full mode and will
         recommend creating a virtual env using sphinx/requirements.txt.
      
         In this case, it **won't** abort the build.
      
      5) If Sphinx is detected and version is equal or righer than
         $rec_version it will return just after detecting the
         version ("quick mode"), not checking if are there any
         missing dependencies.
      
      Just like before, if one wants to install Sphinx from the
      distro, it has to call the script manually and use `--no-virtualenv`
      argument to get the hints for his OS:
      
          You should run:
      
      	sudo dnf install -y python3-sphinx python3-sphinx_rtd_theme
      
      While here, add a small help for the three optional arguments
      for the script.
      
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab+samsung@kernel.org>
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      9b88ad54
  16. Apr 01, 2019
    • Mauro Carvalho Chehab's avatar
      docs: Makefile: use latexmk if available · 28f7c994
      Mauro Carvalho Chehab authored
      
      In the past, Sphinx was generating a LaTex Makefile that would
      run xelatex 3 times. Running it multiple times is needed in order
      to make the indexes right.
      
      However, newer versions of it runs it just once, as it expects
      the machine to use the "latexmk" build, with automatically
      detects the need for rebuilds.
      
      So, add a logic at the Makefile in order to detect if latexmk
      is installed. If so, it will call it.
      
      As an additional bonus, the output of latexmk is a little bit
      better, making easier to identify build problems.
      
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab+samsung@kernel.org>
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      28f7c994
  17. Dec 13, 2018
    • Rob Herring's avatar
      kbuild: Add support for DT binding schema checks · 4f0e3a57
      Rob Herring authored
      
      This adds the build infrastructure for checking DT binding schema
      documents and validating dts files using the binding schema.
      
      Check DT binding schema documents:
      make dt_binding_check
      
      Build dts files and check using DT binding schema:
      make dtbs_check
      
      Optionally, DT_SCHEMA_FILES can be passed in with a schema file(s) to
      use for validation. This makes it easier to find and fix errors
      generated by a specific schema.
      
      Currently, the validation targets are separate from a normal build to
      avoid a hard dependency on the external DT schema project and because
      there are lots of warnings generated.
      
      Cc: Jonathan Corbet <corbet@lwn.net>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Acked-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Cc: Michal Marek <michal.lkml@markovi.net>
      Cc: linux-doc@vger.kernel.org
      Cc: devicetree@vger.kernel.org
      Cc: linux-kbuild@vger.kernel.org
      Signed-off-by: default avatarRob Herring <robh@kernel.org>
      4f0e3a57
  18. Oct 12, 2017
  19. Aug 24, 2017
  20. Jul 23, 2017
  21. May 16, 2017
  22. Oct 10, 2016
  23. Sep 23, 2016
  24. Sep 20, 2016
  25. May 09, 2016
    • Arnd Bergmann's avatar
      [media] samples: v4l: from Documentation to samples directory · 0185f850
      Arnd Bergmann authored
      
      With the new autoksyms support, we can run into a situation where
      the v4l pci skeleton module is the only one using some exported
      symbols that get dropped because they are never referenced by
      the kernel otherwise, causing a build problem:
      
      ERROR: "vb2_dma_contig_memops" [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
      ERROR: "vb2_dma_contig_init_ctx_attrs" [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
      ERROR: "v4l2_match_dv_timings" [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
      ERROR: "v4l2_find_dv_timings_cap" [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
      ERROR: "v4l2_valid_dv_timings" [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
      ERROR: "v4l2_enum_dv_timings_cap" [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
      ERROR: "vb2_dma_contig_cleanup_ctx" [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
      
      Specifically, we do look in the samples directory for users of
      symbols, but not the Documentation directory.
      
      This solves the build problem by moving the connector sample into
      the same directory as the other samples.
      
      Fixes: 23121ca2 ("kbuild: create/adjust generated/autoksyms.h")
      
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      0185f850
  26. Apr 28, 2016
Loading