From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter@lists.netfilter.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Jorge Bastos <mysql.jorge@decimal.pt>
Subject: Re: Compiling 1.3.6
Date: Mon, 09 Oct 2006 17:36:54 +0200 [thread overview]
Message-ID: <452A6C96.2070102@netfilter.org> (raw)
In-Reply-To: <452A6955.6020100@trash.net>
Patrick McHardy wrote:
> Pablo Neira Ayuso wrote:
>
>>min_ip and max_ip type has been changed from u_int32_t to __be32 that is
>>not defined in userspace, this breaks iptables compilation. Attached a
>>patch that recovers the use of u_int32_t. I'm not sure if this is the
>>best fix so let me know what you think.
>
>
> I think we should just define the endian-annotation types in userspace.
> Does this patch fix compilation?
But this breaks previous iptables version with new kernels :(. An
alternative can be exporting ipt_iprange.h to iptables/include although
this is also a hack.
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
next prev parent reply other threads:[~2006-10-09 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 18:41 Compiling 1.3.6 Jorge Bastos
2006-10-08 22:21 ` Pablo Neira Ayuso
2006-10-09 15:23 ` Patrick McHardy
2006-10-09 15:36 ` Pablo Neira Ayuso [this message]
2006-10-09 15:44 ` Pablo Neira Ayuso
2006-10-09 15:58 ` Marco Berizzi
2006-10-09 16:02 ` Patrick McHardy
2006-10-09 16:10 ` Marco Berizzi
2006-10-09 17:23 ` Patrick McHardy
2006-10-09 17:57 ` Jorge Bastos
2006-10-09 16:02 ` Patrick McHardy
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=452A6C96.2070102@netfilter.org \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--cc=mysql.jorge@decimal.pt \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@lists.netfilter.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