From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: netfilter-devel@lists.netfilter.org
Cc: Harald Welte <laforge@netfilter.org>, Patrick McHardy <kaber@trash.net>
Subject: [1/1] ipt_osf: fix ipt_osf compilation on some distros.
Date: Fri, 25 Feb 2005 08:07:37 +0300 [thread overview]
Message-ID: <1109308057.6728.54.camel@uganda> (raw)
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
Some distros have magical header mess, which leads to undefined struct
tcphdr,
when net/tcp.h is not included directly.
Following patch workarounds it.
Signed-off-by: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
--- orig/osf/linux-2.6/net/ipv4/netfilter/ipt_osf.c~ 2005-02-07
18:55:56.000000000 +0300
+++orig/osf/linux-2.6/net/ipv4/netfilter/ipt_osf.c 2005-02-24
12:49:22.329311368 +0300
@@ -47,6 +47,7 @@
#include <net/sock.h>
#include <net/ip.h>
+#include <net/tcp.h>
#include <linux/netfilter_ipv4/ip_tables.h>
P.S. Should I resend lost patch with Subject line
"[1/1] libipt_osf: fix iptables-1.3.0rc1 compilation.", which moves
kernel headers in ipt_osf.h into appropriate ifdef/endif?
--
Evgeniy Polyakov
Crash is better than data corruption -- Arthur Grabowski
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-02-25 5:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 5:07 Evgeniy Polyakov [this message]
2005-02-27 16:32 ` [1/1] ipt_osf: fix ipt_osf compilation on some distros Patrick McHardy
2005-02-27 17:10 ` Evgeniy Polyakov
2005-02-27 17:03 ` Patrick McHardy
2005-02-27 17:39 ` Evgeniy Polyakov
2005-03-01 20:32 ` Patrick McHardy
2005-02-27 17:11 ` [1/2] ipt_osf: move kernel headers into appropriate ifdef/endif area Evgeniy Polyakov
2005-02-27 17:13 ` [2/2] ipt_osf: includes cleanup Evgeniy Polyakov
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=1109308057.6728.54.camel@uganda \
--to=johnpol@2ka.mipt.ru \
--cc=kaber@trash.net \
--cc=laforge@netfilter.org \
--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.