From: Patrick McHardy <kaber@trash.net>
To: Steven Van Acker <deepstar+NRpGDEuW@singularity.be>
Cc: Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
kulnet@kulnet.kuleuven.be
Subject: Re: iptables 1.3.6 compilation issues in libipt_iprange.c (non-existant __be32 type)
Date: Mon, 04 Dec 2006 17:02:08 +0100 [thread overview]
Message-ID: <45744680.5080702@trash.net> (raw)
In-Reply-To: <20061204154845.GA21750@ekonomika.be>
Steven Van Acker wrote:
> Hi,
>
> iptables 1.3.6 does not compile with the 2.6.19 kernel
> because an undefined type __be32 is used in libipt_iprange.c
>
> Apparently, a fix was issued before, which can be found here:
> http://lists.netfilter.org/pipermail/netfilter/2006-October/066954.html
>
> Before I started looking for a patch, I wrote one myself
> and it's a bit different from the one found at the location mentioned
> above.
>
> Instead of #defining the __be32 type "manually", you could also #include
> <linux/types.h>, which defines that datatype.
>
> I'm not sure if it's a good idea to duplicate definitions of datatypes
> in iptables. Is there a purpose I'm overlooking ?
>
> Is it also possible to mention the fix for the __be32 issue on
> netfilter.org ? I'm sure more people will run into it as 2.6.19 is going
> mainstream, and we don't all use the SVN repository to compile iptables
> :)
I've already uploaded a 1.3.7 release to ftp.netfilter.org to fix this
issue (please test :), once the webpage has been updated I'll send out
the announcement.
next prev parent reply other threads:[~2006-12-04 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 15:48 iptables 1.3.6 compilation issues in libipt_iprange.c (non-existant __be32 type) Steven Van Acker
2006-12-04 16:02 ` Patrick McHardy [this message]
2006-12-04 16:52 ` Steven Van Acker
2006-12-04 17:47 ` 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=45744680.5080702@trash.net \
--to=kaber@trash.net \
--cc=deepstar+NRpGDEuW@singularity.be \
--cc=kulnet@kulnet.kuleuven.be \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.