From: Bart De Schuymer <bdschuym@pandora.be>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Jonh Wendell <jonh.wendell@gmail.com>,
netfilter-devel@vger.kernel.org,
Jonh Wendell <jonh.wendell@oiwifi.com.br>
Subject: Re: [PATCH] arptables: build an libarptc.a archive
Date: Sun, 24 Feb 2013 11:09:29 +0100 [thread overview]
Message-ID: <5129E6D9.9000403@pandora.be> (raw)
In-Reply-To: <alpine.LNX.2.01.1302220950030.1652@nerf07.vanv.qr>
Op 22/02/2013 9:50, Jan Engelhardt schreef:
> On Friday 2013-02-22 00:45, Jonh Wendell wrote:
>
>> From: Jonh Wendell <jonh.wendell@oiwifi.com.br>
>>
>> this allows programs to statically link against libarptc.
> A shared library, should anyone ever wish to develop against arptc
> (which I doubt), is much preferable.
I've applied the patch. It's pretty common in embedded systems not to
use shared libraries. If anyone wants a shared library, they'll have to
provide a patch...
Hopefully the new nftables or xtables2 will support arptables and
provide for a better alternative :-)
cheers,
Bart
prev parent reply other threads:[~2013-02-24 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 23:45 [PATCH] arptables: build an libarptc.a archive Jonh Wendell
2013-02-22 8:50 ` Jan Engelhardt
2013-02-24 10:09 ` Bart De Schuymer [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5129E6D9.9000403@pandora.be \
--to=bdschuym@pandora.be \
--cc=jengelh@inai.de \
--cc=jonh.wendell@gmail.com \
--cc=jonh.wendell@oiwifi.com.br \
--cc=netfilter-devel@vger.kernel.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).