From: Steven Van Acker <deepstar@singularity.be>
To: Patrick McHardy <kaber@trash.net>
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, 4 Dec 2006 17:52:50 +0100 [thread overview]
Message-ID: <20061204165250.GA1730@ekonomika.be> (raw)
In-Reply-To: <45744680.5080702@trash.net>
On Mon, Dec 04, 2006 at 05:02:08PM +0100, Patrick McHardy wrote:
> 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.
1.3.7 compiles and works nicely with a 2.6.19 kernel on my system.
Thanks :)
I'm still wondering why <linux/types.h> is not used though. Is it to
avoid complications with older kernels ?
kinds regards,
-- Steven
--
My amazon wishlist:
http://www.amazon.com/gp/registry/1DB4XNEIEQBPB
next prev parent reply other threads:[~2006-12-04 16:52 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
2006-12-04 16:52 ` Steven Van Acker [this message]
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=20061204165250.GA1730@ekonomika.be \
--to=deepstar@singularity.be \
--cc=kaber@trash.net \
--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.