From: Harald Welte <laforge@gnumonks.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org,
"Barry K. Nathan" <barryn@pobox.com>,
Rusty Russell <rusty@linuxcare.com>, Marc Boucher <marc@mbsi.ca>,
James Morris <jmorris@intercode.com.au>
Subject: Re: test13pre2 - netfilter modiles compile failure
Date: Sat, 16 Dec 2000 14:09:41 +0100 [thread overview]
Message-ID: <20001216140941.A7422@coruscant.gnumonks.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10012160015521.11822-100000@penguin.transmeta.com> <Pine.LNX.4.10.10012160031450.11822-100000@penguin.transmeta.com> <20001216115705.A6797@coruscant.gnumonks.org>
In-Reply-To: <20001216115705.A6797@coruscant.gnumonks.org>; from laforge@gnumonks.org on Sat, Dec 16, 2000 at 11:57:05AM +0100
On Sat, Dec 16, 2000 at 11:57:05AM +0100, Harald Welte wrote:
>
> As no other netfilter core team member responded yet, I'm going to provide
> a patch for the 'true library' solution.
well... the 'true library' doesn't make sense, because of the exclusiveness.
In any case there's only one instance of ip_fw_compat inside the kernel:
- ipchains compiled in (ipfwadm option vanishes in 'make menuconfig')
- ipfwadm compiled in (ipchains option vanishes in 'make menuconfig')
- ipchains module loaded: you can't load ipfwadm module
- ipfwadm module loaded: you can't load ipchains module
anyway... here is a patch, which makes the stuff compile and link in all
the combinations I've tried so far. (Please leave the comments, because
we could use them from our patch-o-matic system)
--- linux/net/ipv4/netfilter/Makefile Sat Dec 16 11:59:05 2000
+++ linux-fwcompat/net/ipv4/netfilter/Makefile Sat Dec 16 15:03:02 2000
@@ -14,15 +14,38 @@
# Multipart objects.
list-multi := ip_conntrack.o iptable_nat.o ipfwadm.o ipchains.o
-ip_conntrack-objs := ip_conntrack_standalone.o ip_conntrack_core.o ip_conntrack_proto_generic.o ip_conntrack_proto_tcp.o ip_conntrack_proto_udp.o ip_conntrack_proto_icmp.o
-iptable_nat-objs := ip_nat_standalone.o ip_nat_rule.o ip_nat_core.o ip_nat_proto_unknown.o ip_nat_proto_tcp.o ip_nat_proto_udp.o ip_nat_proto_icmp.o
-ip_nf_compat-objs := ipfwadm_core.o ip_fw_compat.o ip_fw_compat_redir.o ip_fw_compat_masq.o $(ip_conntrack-objs) $(iptable_nat-objs)
-ipfwadm-objs := ipfwadm_core.o
-ipchains-objs := ipchains_core.o
+# objects for the conntrack and NAT core (used by standalone and backw. compat)
+ip_nf_conntrack-objs := ip_conntrack_core.o ip_conntrack_proto_generic.o ip_conntrack_proto_tcp.o ip_conntrack_proto_udp.o ip_conntrack_proto_icmp.o
+ip_nf_nat-objs := ip_nat_core.o ip_nat_proto_unknown.o ip_nat_proto_tcp.o ip_nat_proto_udp.o ip_nat_proto_icmp.o
+# objects for the standalone - connection tracking / NAT
+ip_conntrack-objs := ip_conntrack_standalone.o $(ip_nf_conntrack-objs)
+iptable_nat-objs := ip_nat_standalone.o ip_nat_rule.o $(ip_nf_nat-objs)
+
+# objects for backwards compatibility mode
+ip_nf_compat-objs := ip_fw_compat.o ip_fw_compat_redir.o ip_fw_compat_masq.o $(ip_nf_conntrack-objs) $(ip_nf_nat-objs)
+
+ipfwadm-objs := $(ip_nf_compat-objs) ipfwadm_core.o
+ipchains-objs := $(ip_nf_compat-objs) ipchains_core.o
+
+# connection tracking
obj-$(CONFIG_IP_NF_CONNTRACK) += ip_conntrack.o
+
+# connection tracking helpers
obj-$(CONFIG_IP_NF_FTP) += ip_conntrack_ftp.o
+
+# NAT helpers
+obj-$(CONFIG_IP_NF_FTP) += ip_nat_ftp.o
+
+# generic IP tables
obj-$(CONFIG_IP_NF_IPTABLES) += ip_tables.o
+
+# the three instances of ip_tables
+obj-$(CONFIG_IP_NF_FILTER) += iptable_filter.o
+obj-$(CONFIG_IP_NF_MANGLE) += iptable_mangle.o
+obj-$(CONFIG_IP_NF_NAT) += iptable_nat.o
+
+# matches
obj-$(CONFIG_IP_NF_MATCH_LIMIT) += ipt_limit.o
obj-$(CONFIG_IP_NF_MATCH_MARK) += ipt_mark.o
obj-$(CONFIG_IP_NF_MATCH_MAC) += ipt_mac.o
@@ -31,11 +54,8 @@
obj-$(CONFIG_IP_NF_MATCH_TOS) += ipt_tos.o
obj-$(CONFIG_IP_NF_MATCH_STATE) += ipt_state.o
obj-$(CONFIG_IP_NF_MATCH_UNCLEAN) += ipt_unclean.o
-obj-$(CONFIG_IP_NF_NAT) += iptable_nat.o
-obj-$(CONFIG_IP_NF_FTP) += ip_nat_ftp.o
-obj-$(CONFIG_IP_NF_FILTER) += iptable_filter.o
-obj-$(CONFIG_IP_NF_MANGLE) += iptable_mangle.o
+# targets
obj-$(CONFIG_IP_NF_TARGET_REJECT) += ipt_REJECT.o
obj-$(CONFIG_IP_NF_TARGET_MIRROR) += ipt_MIRROR.o
obj-$(CONFIG_IP_NF_TARGET_TOS) += ipt_TOS.o
@@ -44,8 +64,10 @@
obj-$(CONFIG_IP_NF_TARGET_REDIRECT) += ipt_REDIRECT.o
obj-$(CONFIG_IP_NF_TARGET_LOG) += ipt_LOG.o
-obj-$(CONFIG_IP_NF_COMPAT_IPCHAINS) += ipchains.o ip_nf_compat.o
-obj-$(CONFIG_IP_NF_COMPAT_IPFWADM) += ipfwadm.o ip_nf_compat.o
+# backwards compatibility
+obj-$(CONFIG_IP_NF_COMPAT_IPCHAINS) += ipchains.o
+obj-$(CONFIG_IP_NF_COMPAT_IPFWADM) += ipfwadm.o
+
obj-$(CONFIG_IP_NF_QUEUE) += ip_queue.o
include $(TOPDIR)/Rules.make
@@ -61,6 +83,3 @@
ipchains.o: $(ipchains-objs)
$(LD) -r -o $@ $(ipchains-objs)
-
-ip_nf_compat.o: $(ip_nf_compat-objs)
- $(LD) -r -o $@ $(ip_nf_compat-objs)
--
Live long and prosper
- Harald Welte / laforge@gnumonks.org http://www.gnumonks.org
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M-
V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-16 13:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 4:56 Mohammad A. Haque
2000-12-16 5:52 ` Barry K. Nathan
2000-12-16 6:25 ` Linus Torvalds
2000-12-16 8:06 ` Barry K. Nathan
2000-12-16 8:23 ` Linus Torvalds
2000-12-16 8:42 ` Linus Torvalds
2000-12-16 10:57 ` Harald Welte
2000-12-16 13:09 ` Harald Welte [this message]
2000-12-16 17:51 ` Linus Torvalds
2000-12-17 2:43 ` test13pre2 - ieee1394 " Dax Kelson
2000-12-16 8:54 ` test13pre2 - netfilter modiles " Barry K. Nathan
2000-12-16 6:33 ` Andrew Morton
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=20001216140941.A7422@coruscant.gnumonks.org \
--to=laforge@gnumonks.org \
--cc=barryn@pobox.com \
--cc=jmorris@intercode.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@mbsi.ca \
--cc=rusty@linuxcare.com \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®