Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] latest iptables requires IPv6
Date: Mon, 10 Nov 2008 17:05:05 +1100	[thread overview]
Message-ID: <20081110060504.GA31507@cloud.net.au> (raw)

r23403 | correa | 2008-09-16 12:12:23 +1000 (Tue, 16 Sep 2008) | 1 line

Fix iptables compile error by updating to Makefile.autotools.in and
bumping version to 1.4.1


This new version of iptables requires IPv6. The old iptables.mk patched
the old version to work without it, but that appears to be a lot harder
in this version.

Do the rest of you have IPV6 enabled in uClibc? I don't (unnecessary bloat).
Any suggestions? Anyone got a patch?

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.

thanks
Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

             reply	other threads:[~2008-11-10  6:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  6:05 Hamish Moffatt [this message]
2008-11-10  8:02 ` [Buildroot] latest iptables requires IPv6 Thomas Petazzoni
2008-11-10 23:23   ` Hamish Moffatt

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=20081110060504.GA31507@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