From: Adrian Bunk <bunk@fs.tum.de>
To: Rick Lindsley <ricklind@us.ibm.com>,
Harald Welte <laforge@netfilter.org>,
Nivedita Singhvi <niv@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, coreteam@netfilter.org
Subject: 2.6.9-rc1-mm2: IP_NF_COMPAT_IPCHAINS compilation broken
Date: Wed, 1 Sep 2004 23:07:07 +0200 [thread overview]
Message-ID: <20040901210707.GC3466@fs.tum.de> (raw)
In-Reply-To: <200408312213.i7VMDjF02854@owlet.beaverton.ibm.com>
On Tue, Aug 31, 2004 at 03:13:45PM -0700, Rick Lindsley wrote:
> Getting an error of:
>
> net/built-in.o(.text+0x64047): In function `tcp_in_window':
> net/ipv4/netfilter/ip_conntrack_proto_tcp.c:683: undefined reference to `ip_ct_log_invalid'
> net/built-in.o(.text+0x6431f): In function `tcp_error':
> net/ipv4/netfilter/ip_conntrack_proto_tcp.c:792: undefined reference to `ip_ct_log_invalid'
> net/built-in.o(.text+0x64421):net/ipv4/netfilter/ip_conntrack_proto_tcp.c:817: undefined reference to `ip_ct_log_invalid'
> net/built-in.o(.text+0x64450):net/ipv4/netfilter/ip_conntrack_proto_tcp.c:808: undefined reference to `ip_ct_log_invalid'
> net/built-in.o(.text+0x64487):net/ipv4/netfilter/ip_conntrack_proto_tcp.c:784: undefined reference to `ip_ct_log_invalid'
> net/built-in.o(.text+0x6478a):net/ipv4/netfilter/ip_conntrack_proto_tcp.c:877: more undefined references to `ip_ct_log_invalid' follow
>
> The error is for all references of the LOG_INVALID macro in
> ip_conntrack_proto_tcp.c.
>...
Harald, the LOG_INVALID macro from your
[NETFILTER]: Move error tracking into conntrack protocol helper
patch in Linus' tree breaks compilation with
CONFIG_IP_NF_COMPAT_IPCHAINS=y, since ip_ct_log_invalid isn't available
in this case due to CONFIG_IP_NF_CONNTRACK=n.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-09-01 21:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 6:54 2.6.9-rc1-mm2 Andrew Morton
2004-08-31 8:51 ` 2.6.9-rc1-mm2 Inconsistent kallsyms Helge Hafting
2004-08-31 9:02 ` Andrew Morton
2004-09-01 10:45 ` Helge Hafting
2004-08-31 11:05 ` Paulo Marques
2004-08-31 12:04 ` 2.6.9-rc1-mm2: tdfxfb_lib causes compile error Adrian Bunk
2004-08-31 17:21 ` 2.6.9-rc1-mm2 (compile stats) John Cherry
2004-08-31 17:41 ` [patch] 2.6.9-rc1-mm2: char/pcxx.c doesn't compile Adrian Bunk
2004-08-31 20:18 ` Jesper Juhl
2004-08-31 20:17 ` Adrian Bunk
2004-08-31 20:27 ` Jesper Juhl
2004-08-31 17:47 ` 2.6.9-rc1-mm2: why is DIGIEPCA marked BROKEN? Adrian Bunk
2004-08-31 19:57 ` Christoph Hellwig
2004-08-31 19:59 ` Adrian Bunk
2004-08-31 18:53 ` 2.6.9-rc1-mm2 Martin J. Bligh
2004-08-31 19:16 ` 2.6.9-rc1-mm2 Gene Heskett
2004-08-31 19:45 ` 2.6.9-rc1-mm2 Martin J. Bligh
2004-08-31 19:26 ` 2.6.9-rc1-mm2 Andrew Morton
2004-08-31 18:54 ` 2.6.9-rc1-mm2 Gene Heskett
2004-08-31 19:41 ` 2.6.9-rc1-mm2 Sam Ravnborg
2004-09-01 17:35 ` 2.6.9-rc1-mm2 Tom Rini
2004-09-01 19:23 ` 2.6.9-rc1-mm2 Sam Ravnborg
2004-08-31 22:13 ` 2.6.9-rc1-mm2 Rick Lindsley
2004-09-01 21:07 ` Adrian Bunk [this message]
2004-09-01 7:15 ` 2.6.9-rc1-mm2 Andre Eisenbach
2004-09-01 7:25 ` 2.6.9-rc1-mm2 William Lee Irwin III
2004-09-01 9:15 ` 2.6.9-rc1-mm2 Andre Eisenbach
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=20040901210707.GC3466@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=coreteam@netfilter.org \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niv@us.ibm.com \
--cc=ricklind@us.ibm.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