From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/iproute2: disable iptables support for static build
Date: Tue, 19 May 2015 20:57:09 -0700 [thread overview]
Message-ID: <555C0615.9050608@zacarias.com.ar> (raw)
In-Reply-To: <87egmc5pmf.fsf@dell.be.48ers.dk>
On 19/05/15 12:33, Peter Korsgaard wrote:
> So what about we do:
>
> - Add host-pkgconf to _DEPENDENCIES
> - Add the BR2_STATIC_LIBS conditional for iptables and force
> TC_CONFIG_XT:=n in the else clause.
> - Drop the TC_CONFIG_XT:=y and TC_CONFIG_IPSET:=n overrides
> - Replace the s/-DIPT/-DXT/ handling for iptables with something like:
> $(SED) 's/XT_LIB_DIR/IPT_LIB_DIR/' $(@D)/tc/m_xt.c
> - Drop the IPT_LIB_DIR override in _CONFIGURE_CMDS
>
> Gustavo, you normally take care of iproute2, what do you say?
The iproute2 "build system" periodically changes and breaks things up,
so it doesn't surprise me at all.
Normally the extensions dir (IPT_LIB_DIR) should point to
/usr/lib/xtables as defined by the iptables package.
The ipset bits on tc are to match an ipset (rather than the usual
ip/subnet) to a class to shape/whatever.
I'm currently AFH (away from home) so i don't have my networking testing
rig handy, but in principle it sounds ok as long as the checks in the
makefiles/code have been fixed.
I'll be back on monday, so we can either wait for testing or just go
with it and i'll test when i'm back and scream if something breaks ;)
Caveat: normally netfilter devs don't test/care that much about static
scenarios, they'll take patches but don't expect things to remain
unbroken for an extended period of time.
Regards.
next prev parent reply other threads:[~2015-05-20 3:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 20:54 [Buildroot] [PATCH] package/iproute2: disable iptables support for static build Romain Naour
2015-05-19 19:33 ` Peter Korsgaard
2015-05-20 3:57 ` Gustavo Zacarias [this message]
2015-05-21 21:22 ` Peter Korsgaard
2015-05-23 10:02 ` Romain Naour
2015-05-25 20:32 ` Peter Korsgaard
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=555C0615.9050608@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