Hi.  I am experimenting with using bootstrap+gnulib in a project that
has a library and a command-line tool, and thus needs two gnulib
instances.  The limitation that --with-tests cannot be used in this case
is helpful to repeat in the relevant section, it caused hard to
understand build errors.

Does anyone know whether it will work to have ONE gnulib tests
directory, or if having two gnulib instances causes even a single gnulib
tests directory to be unreliable?  It appears to be working for me with
one directory, so I'll keep doing that to notice breakage.

/Simon

* doc/gnulib-tool.texi (Multiple instances): Remind reader of
--with-tests limitation.
---
 ChangeLog            | 5 +++++
 doc/gnulib-tool.texi | 3 +++
 2 files changed, 8 insertions(+)

diff --git a/ChangeLog b/ChangeLog
index 6c042f567..3bd13281b 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2021-01-04  Simon Josefsson  <simon@josefsson.org>
+
+	* doc/gnulib-tool.texi (Multiple instances): Remind reader of
+	--with-tests limitation.
+
 2021-01-03  Bruno Haible  <bruno@clisp.org>
 
 	iconv, iconv_open: Improve documentation.
diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi
index 3dc6bf002..f3b034f85 100644
--- a/doc/gnulib-tool.texi
+++ b/doc/gnulib-tool.texi
@@ -673,6 +673,9 @@ in the interest of brevity):
     `-- Makefile.am
 @end example
 
+As discussed in @ref{Unit tests}, you may not use @samp{--with-tests}
+for this project since the @code{configure.ac} is shared.
+
 Integration with your code is basically the same as outlined in
 @ref{Initial import} with the one exception that you have to add both
 the macro @code{gl_EARLY} and the macro @code{gl_tools_EARLY} to your
-- 
2.20.1