From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] latest iptables requires IPv6
Date: Tue, 11 Nov 2008 10:23:56 +1100 [thread overview]
Message-ID: <20081110232356.GA29343@cloud.net.au> (raw)
In-Reply-To: <20081110090238.2226416d@surf>
On Mon, Nov 10, 2008 at 09:02:38AM +0100, Thomas Petazzoni wrote:
> Le Mon, 10 Nov 2008 17:05:05 +1100,
> Hamish Moffatt <hamish@cloud.net.au> a ?crit :
>
> > It looks like a few functions in xtables.c could be disabled, and
> > Makefile.am modified not to compile the ipv6-specific programs
> > (ip6tables etc).. all this would need a runtime IPV6 detection because
> > of external toolchains.
>
> Users of external toolchains are supposed to tell in the configuration
> system whether their external toolchain supports IPv6 or not.
>
> See toolchain/external-toolchain/Config.in, option BR2_INET_IPV6.
Thanks, but that doesn't solve the real issue of building without IPV6.
I'll see if I can patch it.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
prev parent reply other threads:[~2008-11-10 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 6:05 [Buildroot] latest iptables requires IPv6 Hamish Moffatt
2008-11-10 8:02 ` Thomas Petazzoni
2008-11-10 23:23 ` Hamish Moffatt [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=20081110232356.GA29343@cloud.net.au \
--to=hamish@cloud.net.au \
--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