texlive[62090] Build/source/doc: c++11/python prereq; more

commits+karl at tug.org commits+karl at tug.org
Sun Feb 20 00:26:31 CET 2022


Revision: 62090
          http://tug.org/svn/texlive?view=revision&revision=62090
Author:   karl
Date:     2022-02-20 00:26:31 +0100 (Sun, 20 Feb 2022)
Log Message:
-----------
c++11/python prereq; more testing/debugging

Modified Paths:
--------------
    trunk/Build/source/doc/ChangeLog
    trunk/Build/source/doc/tlbuild.info
    trunk/Build/source/doc/tlbuild.texi

Modified: trunk/Build/source/doc/ChangeLog
===================================================================
--- trunk/Build/source/doc/ChangeLog	2022-02-19 21:45:30 UTC (rev 62089)
+++ trunk/Build/source/doc/ChangeLog	2022-02-19 23:26:31 UTC (rev 62090)
@@ -1,3 +1,13 @@
+2022-02-19  Karl Berry  <karl at freefriends.org>
+
+	* tlbuild.texi (Prerequisites): C++11 required by HarfBuzz;
+	Python required by ICU tests.
+	(Build problems): move basic idea to "Removing C++11 dependency";
+	not worth its own section.
+	(Build one program): add subsubheadings; mention TEXMFROOT
+	and TEXMFCNF settings to run a program from the build tree.
+	(Build one engine): mention testing hints.
+
 2022-01-11  Karl Berry  <karl at freefriends.org>
 
 	* tlbuild.texi (Prerequisites): mention use of GNU make $@ feature

Modified: trunk/Build/source/doc/tlbuild.info
===================================================================
(Binary files differ)

Modified: trunk/Build/source/doc/tlbuild.texi
===================================================================
--- trunk/Build/source/doc/tlbuild.texi	2022-02-19 21:45:30 UTC (rev 62089)
+++ trunk/Build/source/doc/tlbuild.texi	2022-02-19 23:26:31 UTC (rev 62090)
@@ -1,8 +1,8 @@
 \input texinfo
 @setfilename tlbuild.info
 
- at set version 2021
- at set month-year January 2022
+ at set version 2022
+ at set month-year February 2022
 
 @set mytitle Building @TeX{} Live (@value{version})
 @settitle @value{mytitle}
@@ -96,7 +96,6 @@
 @end menu
 @end ifnottex
 
-
 @node Introduction
 @chapter Introduction
 
@@ -148,7 +147,6 @@
 @url{https://tug.org/texlive/doc.html}, or by invoking the program
 with @samp{--help} (or look at the end of the source).
 
-
 @c The first word of the chapter/section title here is used to
 @c construct the README.* filenames, so choose well.  (Or hack the script.)
 
@@ -210,7 +208,6 @@
 integrating new modules into the TL build system.  (Despite all
 efforts, neither task is easy.)
 
-
 @node Prerequisites
 @chapter Prerequisites
 
@@ -219,30 +216,46 @@
 
 @cindex compilers, C and C++11
 Overall, building the @TL{} programs, when using all libraries from
-the TL source tree, requires C and C++11 compilers and GNU
- at code{make}.  If @code{make} from your @code{PATH} is not GNU @code{make,}
-you can set the @code{MAKE} environment variable to whatever is necessary.
+the TL source tree, requires C and C++11 compilers, GNU @code{make},
+and Python.
 
+ at itemize
+ at item
+If @code{make} from your @code{PATH} is not GNU @code{make}, you can
+set the @code{MAKE} environment variable to whatever is necessary.
+
 @cindex GNU @code{make}, required
 @cindex @code{gmake}, required
- at cindex FreeType
+ at cindex FreeType, requires @code{gmake}
 @cindex @code{$@@} target in normal @code{make} rules
-GNU @code{make} is required only because of some third-party
-libraries, notably FreeType; Automake/Autoconf output in general, and
-the TL-maintained directories, work with any reasonable
+GNU @code{make} is required only because of third-party libraries,
+notably FreeType.  Automake/Autoconf output in general, and the
+TL-maintained directories, work with any reasonable
 @code{make}. at footnote{There is one exception in TL: the
 @code{tangle-sh} and related rules use @code{$@@} to mean the target
 name, a feature not present in all @code{make}s. This could be
-alleviated by some laborious editing, but since there's no way to
-avoid GNU @code{make} for the entire tree, it does not seem worth the
+alleviated by laborious editing, but since there's no way to avoid GNU
+ at code{make} for builds of the entire tree, it does not seem worth the
 trouble.}
 
+ at item
 @cindex C++11, required
+ at cindex @code{dvisvgm}, requires C++11
+ at cindex HarfBuzz, requires C++11
+ at cindex ICU, requires C++11
 A C++11 compiler is similarly required because of the third-party
-library ICU; the program @code{dvisvgm} also requires C++11.  It is
-possible to build everything else with older compilers, but you have
-to remove the C++11-dependent sources.  @xref{Build one package}.
+libraries ICU and HarfBuzz (at least); the program @code{dvisvgm} also
+requires C++11.  It is possible to build what remains with older
+compilers, but you have to remove the C++11-dependent sources.
+ at xref{Build one package}.
 
+ at item
+ at cindex Python, required by ICU
+Python is required by ICU tests.  (If you know how to disable these
+tests and thus eliminate the requirement, please write.)
+
+ at end itemize
+
 A few programs in the tree have additional requirements:
 
 @table @file
@@ -249,11 +262,14 @@
 @item web2c
 @cindex @code{perl}, required by @code{web2c}, etc.
 requires @code{perl} for some tests run by @code{make check}.
+Incidentally, the @TeX{} Live installer (@code{install-tl}) and
+manager (@code{tlmgr}) are also written in Perl, but this does not
+matter for compiling the sources.
 
 @item xdvik
 @itemx xpdfopen
 @cindex X11 development, required by X clients
-require X11 headers and libraries, typically in ``development'' packages
+require X11 headers and libraries, typically in devel(opment) packages
 that are not installed by default.
 
 @item xetex
@@ -261,7 +277,7 @@
 @cindex @code{ApplicationServices} Mac framework, required by @code{xetex}
 @cindex @code{Cocoa} Mac framework, required by @code{xetex}
 requires @file{fontconfig} (again both headers and library), or, for
-MacOSX only, the @code{ApplicationServices} and @code{Cocoa}
+MacOS only, the @code{ApplicationServices} and @code{Cocoa}
 frameworks.
 
 @item xindy
@@ -302,10 +318,9 @@
 such as @code{autoconf} or @code{makeinfo} are still being run, check
 your timestamps---notably, @code{use-commit-times} must be set to
 @code{yes} in your Subversion configuration (@pxref{Build system
-tools}).  Barring buggy commits, no infrastructure tools are needed to
-do a normal build.
+tools}).  No infrastructure tools are needed to do a normal build
+(barring bugs).
 
-
 @node Building
 @chapter Building
 
@@ -333,7 +348,6 @@
 
 @menu
 * Build iteration::     What @code{configure} and @code{make} do in TL.
-* Build problems::      If the build fails.
 * Build in parallel::   Simultaneous @code{make} processes.
 * Build distribution::  Making a distribution tarball.
 * Build one package::   Example of working on just one program.
@@ -341,7 +355,6 @@
 * Cross compilation::   Building on host X for target Y.
 @end menu
 
-
 @node Build iteration
 @section Build iteration
 
@@ -374,21 +387,6 @@
 all the library and program modules, and finds (should find) nothing
 to be done.
 
-
- at node Build problems
- at section Build problems
-
- at cindex build problems
- at cindex problems with build
- at cindex failure to build
- at vindex --no-clean Build @r{option}
-If configuring or building a module fails, you should first try to
-find and fix the problem.  Failing that, a possible workaround is to
-remove the subdirectory for that module from the build tree (so
- at code{configure} won't try to run there, and finally rerun the top
-level @code{make} (or @file{./Build} @code{--no-clean}).
-
-
 @node Build in parallel
 @section Build in parallel
 
@@ -410,7 +408,6 @@
 using a configure cache file, i.e., specifying the @code{configure}
 option @code{-C} (recommended).
 
-
 @node Build distribution
 @section Build distribution
 
@@ -429,7 +426,6 @@
 We do not actually distribute any such tarball, and have no plans to
 do so.
 
-
 @node Build one package
 @section Build one package
 
@@ -446,8 +442,8 @@
 library, first building any required libraries.
 
 Here is an example from start to finish for working on
- at code{dvipdfm-x}.  (Unfortunately, this does not suffice for building
-the @TeX{} engines; see the next section.)
+ at code{dvipdfm-x}.  Unfortunately, this does not suffice for building
+the @TeX{} engines; see the next section.
 
 @example
 mkdir mydir && cd mydir  # new working directory
@@ -466,11 +462,21 @@
 # Do the make:
 make >&outm || echo fail
 
-# Test:
+# Run the tests:
 cd texk/dvipdfm-x
 make check
+
+# Run the new binary in the buil tree, finding support files
+# in a separate tree for a TeX Live release YYYY
+# (Bourne shell syntax):
+TEXMFROOT=/usr/local/texlive/YYYY \
+TEXMFCNF=$TEXMFROOT/texmf-dist/web2c \
+./xdvipdfmx ...
 @end example
 
+ at vindex TEXMFROOT @r{for running standalone}
+ at vindex TEXMFCNF @r{for running standalone}
+
 Then you can modify source files in @file{mydir/texk/dvipdfm-x} and
 rerun @code{make} in @file{mydir/Work/texk/dvipdfm-x} to rebuild; that
 build directory is where the binary ends up and where you can run a
@@ -489,8 +495,10 @@
 is also a good idea to run @code{make check} after making any changes,
 to ensure that whatever tests have been written still pass.
 
+ at subsubheading Reducing source download size
+
 @cindex size of source tree
-Finally, the above retrieves the entire TL source tree (several
+The above retrieves the entire TL source tree (several
 hundred megabytes). It is natural to ask if this is really necessary.
 Strictly speaking, the answer is no, but it is vastly more convenient
 to do so. If you cut down the source tree, you must also give
@@ -502,6 +510,19 @@
 @url{http://pdftex.org}), which is indeed such a cut-down TL source
 tree.
 
+ at subsubheading GCC used by default
+
+ at vindex CC=@var{c-compiler}
+ at vindex CXX=@var{c++-compiler}
+ at vindex OBJCXX=@var{objc-compiler}
+ at pindex gcc at r{, default compilers}
+By default, the @code{gcc} compilers will be used if present;
+otherwise, individual packages may use something different.  You can
+explicitly specify the compilers to be used with the environment
+variables @code{CC}, @code{CXX}, and @code{OBJCXX}.
+
+ at subsubheading Removing C+11 dependency
+
 @cindex C++11, removing dependent sources
 Some libraries and programs require C++11; one such is XeTeX.  If you
 want to build with an older compiler lacking such support, you need to
@@ -516,23 +537,26 @@
 
 @vindex --enable-missing @r{to ignore dependencies}
 Also, even with @code{--disable-all-pkgs}, dependencies are (currently)
-checked.  One notable case: if a (non-MacOSX) system does not have
+checked.  One notable case: if a (non-MacOS) system does not have
 @code{fontconfig}, Xe at TeX{} cannot be built (@pxref{Prerequisites}),
 and @code{configure} will terminate even with @code{--disable-xetex}.
 To proceed without such dependencies, specify @code{--enable-missing}
 also.
 
-Patches to improve all this would be most welcome.
+As of 2022, HarfBuzz also requires C++11.  Therefore even more would
+have to be disabled and removed, notably including @code{luahbtex},
+the standard engine used for Lua at LaTeX{}.  Removing that would not
+be acceptable for builds intended for distribution; but perhaps for
+testing the above information could still be useful.
 
- at vindex CC=@var{c-compiler}
- at vindex CXX=@var{c++-compiler}
- at vindex OBJCXX=@var{objc-compiler}
- at pindex gcc at r{, default compilers}
-By default, the @code{gcc} compilers will be used if present;
-otherwise, individual packages may use something different.  You can
-explicitly specify the compilers to be used with the environment
-variables @code{CC}, @code{CXX}, and @code{OBJCXX}.
+ at cindex removing build directories
+ at cindex @code{configure} problems, work around by removing
+In general, the TL @code{configure} will run in all directories.
+Therefore a general workaround for build problems is to remove failing
+directories from the tree, and also specify the relevant
+ at code{--disable-...} option(s).
 
+Patches to improve all this would be most welcome.
 
 @node Build one engine
 @section Build one engine
@@ -576,9 +600,36 @@
 Then it is necessary to again specify the target engine (@code{tex},
 in the above) in the @code{make}.
 
-All this is somewhat unfortunate.  We hope to improve the situation in
-the future.  Patches are welcome.
+All these complications are rather unfortunate.  Patches are welcome.
 
+ at subsubheading Testing one engine
+
+To run only the tests for a given engine, say @code{hitex}:
+
+ at example
+make -C $ww check SUBDIRS=. TESTS='$(hitex_tests)' 
+ at end example
+
+ at noindent where @code{$ww} is the web2c build directory, that is,
+ at file{ww=/wherever/Build/source/Work/texk/web2c}.
+
+It's also possible to run individual tests the same way, using the test
+name exactly as specified in the @file{.am} file:
+
+ at example
+make -C $ww check SUBDIRS=. TESTS=hitexdir/tests/hello.test
+ at end example
+
+ at vindex --no-print-directory @r{GNU make option}
+If you get tired of looking at the @samp{Entering}/@samp{Leaving
+directory} lines, you can add the (GNU) make option
+ at code{--no-print-dir}.
+
+You may find it useful to put lengthy incantations like this into a
+trivial shell script with a short name (say, @code{hitst}).  Then you
+just run @code{hitst} and edit the file when necessary to change
+things around.
+
 @node Cross compilation
 @section Cross compilation
 
@@ -600,7 +651,7 @@
 (@pxref{Hosts and Cross-Compilation,,, autoconf, GNU Autoconf}).
 
 In order to build, e.g., 32-bit binaries with @command{clang} on a 64-bit
-MacOSX system one could use:
+MacOS system one could use:
 
 @example
 TL_BUILD_ENV="CC='clang -arch i386' \
@@ -727,7 +778,6 @@
 Building @code{xindy} requires running the host system @code{clisp}
 binary, thus cross compilation is painful, but possible.
 
-
 @node Installing
 @chapter Installing
 
@@ -757,7 +807,6 @@
 * Distro builds::               Configuring and building for OS distributions.
 @end menu
 
-
 @node Installation directories
 @section Installation directories
 
@@ -817,7 +866,6 @@
 @file{Master/bin/@var{tl-platform}}.  The other files and directories
 that end up in @file{./inst/} are ignored.
 
-
 @node Linked scripts
 @section Linked scripts
 
@@ -858,7 +906,6 @@
 information about building those exceptions, as well as the @code{xz}
 and @code{wget} programs that are used in the TL infrastructure.)
 
-
 @node Distro builds
 @section Distro builds
 
@@ -931,7 +978,6 @@
 article needs updating in the future, perhaps we will merge it into
 this document.)
 
-
 @node Layout and infrastructure
 @chapter Layout and infrastructure
 
@@ -953,7 +999,6 @@
 * Extending @TL{}::         Adding a new module.
 @end menu
 
-
 @node Build system tools
 @section Build system tools
 
@@ -1012,7 +1057,6 @@
 @file{config.h.in} (or @file{c-auto.in}), and finally all
 @file{Makefile.in} files.
 
-
 @node Top-level directories
 @section Top-level directories
 
@@ -1068,7 +1112,6 @@
 be changed by setting environment variables before running it; see the
 script source.
 
-
 @node Autoconf macros
 @section Autoconf macros
 
@@ -1130,7 +1173,6 @@
 modules.
 @end defmac
 
-
 @node Macros for programs
 @subsection Macros for programs
 
@@ -1158,7 +1200,6 @@
 Call @code{AC_PROG_LEX} and add the flag @code{-l} for @code{flex}.
 @end defmac
 
-
 @node Macros for compilers
 @subsection Macros for compilers
 
@@ -1205,7 +1246,6 @@
 This macro caches its result in the @code{kpse_cv_cxx_hack} variable.
 @end defmac
 
-
 @node Macros for libraries
 @subsection Macros for libraries
 
@@ -1218,7 +1258,6 @@
 @code{-D at var{extra-define}}) to @var{variable}.
 @end defmac
 
-
 @node Macros for library and header flags
 @subsection Macros for library and header flags
 
@@ -1287,7 +1326,6 @@
 KPSE_RESTORE_FLAGS # @r{restore @code{CPPFLAGS} and @code{LIBS}}
 @end example
 
-
 @node Macros for Windows
 @subsection Macros for Windows
 
@@ -1338,7 +1376,6 @@
 @code{@var{bar}->@var{foo}} for Unix-like systems.
 @end defmac
 
-
 @node Library modules
 @section Library modules
 
@@ -1426,7 +1463,6 @@
 @code{--with-system-libpng}, which then uses @code{pkg-config} to
 determine the flags required for the system library.
 
-
 @node @code{zlib} library
 @subsection The @code{zlib} library in @file{libs/zlib}
 
@@ -1440,7 +1476,6 @@
 @code{--with-zlib-libdir} to specify non-standard locations of the
 @code{zlib} headers and/or library.
 
-
 @node @code{freetype} library
 @subsection The @code{freetype} library in @file{libs/freetype2}
 
@@ -1459,7 +1494,6 @@
 The flags required for the system library are obtained through
 @code{freetype-config}.
 
-
 @node @code{kpathsea} library
 @subsection The @code{kpathsea} library in @file{texk/kpathsea}
 
@@ -1495,7 +1529,6 @@
 @code{-no-mktex=tfm} for the @TeX{}-like engines override this
 default.
 
-
 @node Program modules
 @section Program modules
 
@@ -1511,7 +1544,6 @@
 * @code{asymptote}::       @file{utils/asymptote}
 @end menu
 
-
 @node @code{t1utils} package
 @subsection The @code{t1utils} package in @file{utils/t1utils}
 
@@ -1529,7 +1561,6 @@
 @noindent specifying the module name without any dependencies, and
 supplies the configure option @code{--disable-t1utils}.
 
-
 @node @code{xindy} package
 @subsection The @code{xindy} package in @file{utils/xindy}
 
@@ -1560,7 +1591,6 @@
 specify more @code{configure} options to be seen at the top level,
 with @file{ac/xindy.ac} also included by @file{configure.ac}.
 
-
 @node @code{xdvik} package
 @subsection The @code{xdvik} package in @file{texk/xdvik}
 
@@ -1591,7 +1621,6 @@
 @file{configure.ac} and supplies the configure option
 @code{--with-xdvi-x-toolkit} also seen at the top level.
 
-
 @node @code{asymptote}
 @subsection The subdirectory @file{utils/asymptote}
 
@@ -1605,7 +1634,6 @@
 installed independently, but are included on the TL DVD together with
 their support files.  See @url{https://tug.org/build.html#asymptote}.
 
-
 @node Extending @TL{}
 @section Extending @TL{}
 
@@ -1630,7 +1658,6 @@
 * Adding a new @TeX{}-specific library module::
 @end menu
 
-
 @node Adding a new program module
 @subsection Adding a new program module
 
@@ -1854,7 +1881,6 @@
 @file{m4/kpse-pkgs.m4} must be extended by the line:@*@ @ @
 @code{AC_REQUIRE([KPSE_ at var{LIB}_SYSTEM_FLAGS])}
 
-
 @node Adding a new @TeX{}-specific library module
 @subsection Adding a new @TeX{}-specific library module
 
@@ -1879,7 +1905,6 @@
 The fragment @code{ac/withenable.ac} must use @code{KPSE_WITH_TEXLIB}.
 @end itemize
 
-
 @node Configure options
 @chapter Configure options
 
@@ -1916,7 +1941,6 @@
 * Variables for configure::
 @end menu
 
-
 @node Global configure options
 @section Global configure options
 
@@ -1939,7 +1963,6 @@
 * @code{--without-x}::
 @end menu
 
-
 @node @code{--disable-native-texlive-build}
 @subsection @code{--disable-native-texlive-build}
 
@@ -1962,7 +1985,6 @@
 use this option to enable TL-specific adaptations, such as
 installation paths.
 
-
 @node @code{--prefix} @code{--bindir} @dots{}
 @subsection @code{--prefix}, @code{--bindir}, @dots{}
 
@@ -1977,7 +1999,6 @@
 if set, on the @code{make} command line (@pxref{Staged Installs, ,
 Installation in a temporary location, automake, GNU Automake}).
 
-
 @node @code{--disable-largefile}
 @subsection @code{--disable-largefile}
 
@@ -1995,7 +2016,6 @@
 With LFS, there is no fixed limit on the size of PDF files created by
 @file{pdftex} or PostScript files created by @file{dvips}.
 
-
 @node @code{--disable-missing}
 @subsection @code{--disable-missing}
 
@@ -2004,7 +2024,6 @@
 must be disabled, e.g., due to missing libraries.  This can help when
 figuring out a specific (sub)set of modules to enable.
 
-
 @node @code{--enable-compiler-warnings=}@var{level}
 @subsection @code{--enable-compiler-warnings=}@var{level}
 
@@ -2017,7 +2036,6 @@
 consistently used in all library and program modules.  At present,
 these warning flags assume options from the GNU compilers.
 
-
 @node @code{--enable-cxx-runtime-hack}
 @subsection @code{--enable-cxx-runtime-hack}
 
@@ -2025,7 +2043,6 @@
 try to statically link with @code{libstdc++}, thus improving
 portability of the resulting binary.  @xref{Macros for compilers}.
 
-
 @node @code{--enable-maintainer-mode}
 @subsection @code{--enable-maintainer-mode}
 
@@ -2036,7 +2053,6 @@
 rebuilds infrastructure files as needed.  @xref{maintainer-mode,,
 @code{missing} and @code{AM_MAINTAINER_MODE}, automake, GNU Automake}.
 
-
 @node @code{--enable-multiplatform}
 @subsection @code{--enable-multiplatform}
 
@@ -2053,7 +2069,6 @@
 @code{bindir} and @code{libdir} are automatically propagated to all
 subdirectories.
 
-
 @node @code{--enable-shared}
 @subsection @code{--enable-shared}
 
@@ -2062,7 +2077,6 @@
 @file{libkpathsea}.  This is not allowed for a native TL build (i.e.,
 @code{--disable-native-texlive-build} must also be specified).
 
-
 @node @code{--enable-silent-rules}
 @subsection @code{--enable-silent-rules}
 
@@ -2074,7 +2088,6 @@
 command line to get more verbosity, or @code{V=0} to get less,
 regardless of this option.
 
-
 @node @code{--without-ln-s}
 @subsection @code{--without-ln-s}
 
@@ -2083,7 +2096,6 @@
 binaries for a Unix-like system.  However, @code{make install} will
 not create anything useful, and might fail.
 
-
 @node @code{--without-x}
 @subsection @code{--without-x}
 
@@ -2090,7 +2102,6 @@
 @vindex --without-x
 Disable all programs using the X Window System.
 
-
 @node Program-specific configure options
 @section Program-specific configure options
 
@@ -2110,7 +2121,6 @@
 * Configure options for @file{utils/xindy}::
 @end menu
 
-
 @node @code{--enable- at var{prog}} @code{--disable- at var{prog}}
 @subsection @code{--enable- at var{prog}}, @code{--disable- at var{prog}}
 
@@ -2118,7 +2128,6 @@
 @vindex --disable- at var{prog}
 Do or do not build and install the program(s) of module @code{@var{prog}}.
 
-
 @node @code{--disable-all-pkgs}
 @subsection @code{--disable-all-pkgs}
 
@@ -2134,7 +2143,6 @@
 explicitly disabled or specify @code{disable} in their
 @file{ac/withenable.ac} fragment.
 
-
 @node Configure options for @file{texk/web2c}
 @subsection Configure options for @file{texk/web2c}
 
@@ -2231,7 +2239,6 @@
 @noindent @code{--disable-synctex}
 @*Do not build the @code{SyncTeX} library and tool.
 
-
 @node Configure options for @file{texk/bibtex-x}
 @subsection Configure options for @file{texk/bibtex-x}
 
@@ -2249,7 +2256,6 @@
 @noindent @code{--disable-bibtexu}@*Do not build the @file{bibtexu} program
 (building @file{bibtexu} requires @code{ICU} libraries).
 
-
 @node Configure options for @file{texk/dvipdfm-x}
 @subsection Configure options for @file{texk/dvipdfm-x}
 
@@ -2273,7 +2279,6 @@
 @noindent @code{--disable-xdvipdfmx}@*Do not build the @file{xdvipdfmx}
 program.
 
-
 @node Configure options for @file{texk/dvisvgm}
 @subsection Configure options for @file{texk/dvisvgm}
 
@@ -2297,7 +2302,6 @@
 @code{--with-libgs-libdir=@var{dir}}@*Specify non-standard locations
 of the Ghostscript headers and library.
 
-
 @node Configure options for @file{texk/texlive}
 @subsection Configure options for @file{texk/texlive}
 
@@ -2307,7 +2311,6 @@
 scripts'' (@pxref{Linked scripts}), except for the TL scripts required
 to run @code{texlinks}.
 
-
 @node Configure options for @file{texk/xdvik}
 @subsection Configure options for @file{texk/xdvik}
 
@@ -2332,7 +2335,6 @@
 @noindent @code{--enable-xi2-scrolling}@*Use XInput 2.1 ``smooth scrolling''
 if available (default: yes, except for a native TL build).
 
-
 @node Configure options for @file{utils/xindy}
 @subsection Configure options for @file{utils/xindy}
 
@@ -2359,7 +2361,6 @@
 the installed version of @file{clisp} (which must be identical to the
 one used to build @file{xindy}).
 
-
 @node Library-specific configure options
 @section Library-specific configure options
 
@@ -2473,7 +2474,6 @@
 
 @end vtable
 
-
 @node Coding conventions
 @chapter Coding conventions
 
@@ -2494,7 +2494,6 @@
 * Const::
 @end menu
 
-
 @node Declarations and definitions
 @section Declarations and definitions
 
@@ -2607,7 +2606,6 @@
 otherwise must be carefully analyzed to make sure that they cannot
 cause the modification of quantities supposed to be constant.
 
-
 @node Continuous integration
 @chapter Continuous integration
 
@@ -2628,7 +2626,6 @@
 * Releases on Github::
 @end menu
 
-
 @node Transfer from Subversion to Github
 @section Transfer from Subversion to Github
 



More information about the tex-live-commits mailing list.