From: Adrian Bunk <bunk@stusta.de>
To: Athanasius <link@miggy.org>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
coreteam@netfilter.org
Cc: netfilter-devel@lists.netfilter.org, netdev@vger.kernel.org
Subject: netfilter: IP_NF_CONNTRACK_NETLINK=y, IP_NF_NAT=m compile error
Date: Sat, 1 Apr 2006 11:18:47 +0200 [thread overview]
Message-ID: <20060401091847.GC28310@stusta.de> (raw)
In-Reply-To: <20060331170916.GL28030@miggy.org>
On Fri, Mar 31, 2006 at 06:09:16PM +0100, Athanasius wrote:
> On Tue, Mar 28, 2006 at 05:39:32PM +0100, Athanasius wrote:
> > CC init/version.o
> > LD init/built-in.o
> > LD .tmp_vmlinux1
> > net/built-in.o(.text+0x7c990): In function `ctnetlink_parse_nat_proto':
> > : undefined reference to `ip_nat_proto_find_get'
> > net/built-in.o(.text+0x7c9b2): In function `ctnetlink_parse_nat_proto':
> > : undefined reference to `ip_nat_proto_put'
> > net/built-in.o(.text+0x7d695): In function `ctnetlink_change_conntrack':
> > : undefined reference to `ip_nat_setup_info'
> > net/built-in.o(.text+0x7da9f): In function `ctnetlink_create_conntrack':
> > : undefined reference to `ip_nat_setup_info'
> > make: *** [.tmp_vmlinux1] Error 1
> ...
> > CONFIG_IP_NF_TARGET_TCPMSS=m
> > CONFIG_IP_NF_NAT=m
> > CONFIG_IP_NF_NAT_NEEDED=y
> > CONFIG_IP_NF_TARGET_MASQUERADE=m
>
> ...
>
> It looks like the problem was that "CONFIG_IP_NF_NAT=m". I changed
> this to 'y' and things look to be compiling fine now.
>...
First of all thanks for your report.
More exactly, it's the combination CONFIG_IP_NF_CONNTRACK_NETLINK=y,
CONFIG_IP_NF_NAT=m.
Can someone who understands the netfilter dependencies please look into
this bug?
It's present in both 2.6.16.1 and 2.6.16-mm2.
> -Ath
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
prev parent reply other threads:[~2006-04-01 9:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 6:23 Linux v2.6.16 Linus Torvalds
2006-03-20 12:02 ` 2.6.16.x will be a long-living kernel series Adrian Bunk
2006-03-20 12:05 ` Arjan van de Ven
2006-03-20 12:12 ` Adrian Bunk
2006-03-20 13:03 ` Arjan van de Ven
2006-03-24 0:22 ` Adrian Bunk
2006-03-20 19:22 ` Jan Engelhardt
2006-03-20 17:19 ` Linux v2.6.16 Joe Korty
2006-03-20 19:04 ` Jeff Garzik
2006-03-20 19:25 ` Jan Engelhardt
2006-03-20 19:32 ` Joe Korty
2006-03-20 19:33 ` Linus Torvalds
2006-03-20 21:05 ` Andreas Schwab
2006-03-20 22:52 ` Matthias Andree
2006-03-22 5:22 ` Peter Williams
2006-03-22 6:31 ` Ashok Raj
2006-03-22 13:08 ` Ashok Raj
2006-03-22 13:25 ` Michal Piotrowski
2006-03-22 17:39 ` Rafael J. Wysocki
2006-03-22 17:54 ` Ashok Raj
2006-03-22 18:11 ` Rafael J. Wysocki
2006-03-22 18:27 ` Ashok Raj
2006-03-22 20:40 ` Rafael J. Wysocki
2006-03-22 21:00 ` Ashok Raj
2006-03-22 21:36 ` Rafael J. Wysocki
2006-03-22 22:27 ` Peter Williams
2006-03-28 16:39 ` Linux v2.6.16(.1) - compile failure Athanasius
2006-03-31 17:09 ` 'make oldconfig' sub-optimal 2.6.15 -> 2.6.16(.1) (was Re: Linux v2.6.16(.1) - compile failure) Athanasius
2006-04-01 9:18 ` Adrian Bunk [this message]
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=20060401091847.GC28310@stusta.de \
--to=bunk@stusta.de \
--cc=coreteam@netfilter.org \
--cc=link@miggy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=torvalds@osdl.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.