From: Jan Engelhardt <jengelh@inai.de>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH] build: resolve link failure for ip6t_NETMAP
Date: Sun, 2 Dec 2012 19:16:48 +0100 [thread overview]
Message-ID: <1354472208-25759-1-git-send-email-jengelh@inai.de> (raw)
Link stage of libip6t_NETMAP failed since recently.
CCLD libip6t_NETMAP.so
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld:
cannot find -lip6tc
Signed-off-by: Jan Engelhardt <jengelh@inai.de>
---
Retrievable through
git://git.inai.de/iptables master
extensions/GNUmakefile.in | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/extensions/GNUmakefile.in b/extensions/GNUmakefile.in
index e71e3ff..68e0b9b 100644
--- a/extensions/GNUmakefile.in
+++ b/extensions/GNUmakefile.in
@@ -101,7 +101,8 @@ libxt_state.so: libxt_conntrack.so
ln -fs $< $@
# Need the LIBADDs in iptables/Makefile.am too for libxtables_la_LIBADD
-ip6t_NETMAP_LIBADD = -lip6tc
+ip6t_NETMAP_LIBADD = -L${top_builddir}/libiptc/.libs \
+ -L${top_builddir}/libiptc -lip6tc
xt_RATEEST_LIBADD = -lm
xt_statistic_LIBADD = -lm
--
1.7.10.4
next reply other threads:[~2012-12-02 18:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 18:16 Jan Engelhardt [this message]
2012-12-03 13:12 ` [PATCH] build: resolve link failure for ip6t_NETMAP Pablo Neira Ayuso
2012-12-03 15:58 ` Jan Engelhardt
2012-12-04 12:16 ` Pablo Neira Ayuso
2012-12-04 13:42 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2012-12-31 0:51 [PATCH] extensions: fix linking against -lip6tc Mike Frysinger
2012-12-31 5:54 ` [PATCH] build: resolve link failure for ip6t_NETMAP Jan Engelhardt
2013-01-02 4:03 ` Mike Frysinger
2013-01-02 8:42 ` Jan Engelhardt
2013-01-02 8:47 ` Jan Engelhardt
2013-01-02 17:23 ` Mike Frysinger
2013-01-02 23:50 ` Pablo Neira Ayuso
2013-01-11 23:34 ` Dmitry V. Levin
2013-01-12 0:00 ` Dmitry V. Levin
2013-01-12 1:37 ` Jan Engelhardt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1354472208-25759-1-git-send-email-jengelh@inai.de \
--to=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 NNTP newsgroup(s).