Collin Funk wrote:
> This section of documentation discusses using gnulib-tool to build and
> test Gnulib. I've applied this patch to document Python should be
> installed.
Thanks.
And Java (along with C#) is not needed for Gnulib; no unit test runs Java
or C# code, AFAICS. The real tests of Java and C# functionality are in
GNU gettext and GNU bison.
2024-10-29 Bruno Haible <br...@clisp.org>
doc: Don't mention Java dependency.
* doc/build-automation.texi (Building gnulib): Remove Java from the
needed tools.
diff --git a/doc/build-automation.texi b/doc/build-automation.texi
index 54aa218996..f4c090548b 100644
--- a/doc/build-automation.texi
+++ b/doc/build-automation.texi
@@ -10,8 +10,8 @@
Install the proper development tools. To build and test all of
Gnulib, you will need development tools for the programming languages
-C, C++, Java, Perl, and Python along with standard POSIX utilities such
-as @command{awk}, @command{make} and @command{sh}. You will also need
+C, C++, Python, and Perl, along with standard POSIX utilities such
+as @command{awk}, @command{make}, and @command{sh}. You will also need
development tools that include Autoconf, Automake, Bison, Gettext,
Git, GNU M4, Gperf, Libtool, and Texinfo. Some of these tools are
needed only by some modules. More details can be found in Gnulib's
