From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Reuben Thomas <rrt@sc3d.org>
Subject: Re: Typo in gnulib-tool.texi?
Date: Mon, 12 Apr 2021 21:10:55 +0200 [thread overview]
Message-ID: <39473279.aAY5y8aAkB@omega> (raw)
In-Reply-To: <CAOnWdojecoU9tQ=OHRJM8ifU5qBULP3d+==+t7n+e_BK1+bERg@mail.gmail.com>
Hi Reuben,
> In the following text, describing how to use multiple gnulib installations:
>
> Correspondingly for the programs you will have to add something like
> this:
>
> ...
> AM_CPPFLAGS = -I$(top_srcdir)/src/gnulib -I$(top_builddir)/src/gnulib
> ...
> LIBADD = $(top_builddir)/src/gnulib/libgnutools.la
>
> should LIBADD be LDADD, since we're talking here about building a program,
> not a library?
Right. Thanks for the report. Fixed:
2021-04-12 Bruno Haible <bruno@clisp.org>
doc: Fix confusion between LIBADD and LDADD.
Reported by Reuben Thomas <rrt@sc3d.org> in
<https://lists.gnu.org/archive/html/bug-gnulib/2021-04/msg00102.html>.
* doc/gnulib-tool.texi (Multiple instances): For programs, use LDADD,
not LIBADD.
diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi
index 97881f1..465bb42 100644
--- a/doc/gnulib-tool.texi
+++ b/doc/gnulib-tool.texi
@@ -715,7 +715,7 @@ this:
...
AM_CPPFLAGS = -I$(top_srcdir)/src/gnulib -I$(top_builddir)/src/gnulib
...
-LIBADD = $(top_builddir)/src/gnulib/libgnutools.la
+LDADD = $(top_builddir)/src/gnulib/libgnutools.la
...
@end example
prev parent reply other threads:[~2021-04-12 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 20:49 Typo in relocatable-maint.texi? Reuben Thomas
2021-04-12 19:10 ` Bruno Haible [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39473279.aAY5y8aAkB@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=rrt@sc3d.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).