From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: pablo@netfilter.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH iptables] nfnl_osf: use the right nfnetlink lib
Date: Tue, 02 Apr 2013 16:38:42 +0200 [thread overview]
Message-ID: <515AED72.20300@6wind.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1303291620200.11529@nerf07.vanv.qr>
Le 29/03/2013 16:20, Jan Engelhardt a écrit :
> On Friday 2013-03-29 15:21, Nicolas Dichtel wrote:
>
>> If the user specify libnfnetlink_LIBS during the configure, we must use it.
>>
>> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
>> ---
>> utils/Makefile.am | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/utils/Makefile.am b/utils/Makefile.am
>> index f1bbfc5..8a85396 100644
>> --- a/utils/Makefile.am
>> +++ b/utils/Makefile.am
>> @@ -7,4 +7,4 @@ AM_CPPFLAGS = ${regular_CPPFLAGS} -I${top_builddir}/include \
>> sbin_PROGRAMS = nfnl_osf
>> pkgdata_DATA = pf.os
>>
>> -nfnl_osf_LDADD = -lnfnetlink
>> +nfnl_osf_LDADD = ${libnfnetlink_LIBS} -lnfnetlink
>
> You really should remove -lnfnetlink :)
>
Not sure to understand your comment. ${libnfnetlink_LIBS} contains only
something like '-L/path/to/my/lib'.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-04-02 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 14:21 [PATCH iptables] nfnl_osf: use the right nfnetlink lib Nicolas Dichtel
2013-03-29 15:20 ` Jan Engelhardt
2013-04-02 14:38 ` Nicolas Dichtel [this message]
2013-04-03 2:17 ` Jan Engelhardt
2013-04-03 9:21 ` [PATCH iptables v2] " Nicolas Dichtel
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=515AED72.20300@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.