From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] iptables: disable static for dynamic builds
Date: Tue, 21 Oct 2014 14:06:03 -0300 [thread overview]
Message-ID: <5446927B.90908@zacarias.com.ar> (raw)
In-Reply-To: <20141021190227.05483ab6@free-electrons.com>
On 10/21/2014 02:02 PM, Thomas Petazzoni wrote:
> Dear Gustavo Zacarias,
>
> On Tue, 21 Oct 2014 13:58:14 -0300, Gustavo Zacarias wrote:
>
>> +# Building static causes ugly warnings on some plugins
>> +IPTABLES_CONF_OPTS = --libexecdir=/usr/lib --with-kernel=$(STAGING_DIR)/usr \
>> + $(if $(BR2_PREFER_STATIC_LIB),,--disable-static)
>
> Quick related question: does iptables work properly for purely static
> builds?
I haven't tried in a while, but probably yes, since the effect of both
enables was quite similar, otherwise normally extensions live in
/usr/lib/xtables/* as dynamic objects (where you can add new ones, which
is what xtables-addons does besides adding new kernel modules, with the
scenario right now being every extension linked into the iptables
/usr/sbin/xtables-multi binary).
Regards.
next prev parent reply other threads:[~2014-10-21 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 16:58 [Buildroot] [PATCH] iptables: disable static for dynamic builds Gustavo Zacarias
2014-10-21 17:02 ` Thomas Petazzoni
2014-10-21 17:06 ` Gustavo Zacarias [this message]
2014-10-21 17:04 ` Yann E. MORIN
2014-10-22 19:38 ` Thomas Petazzoni
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=5446927B.90908@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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