From: Eric Dumazet <eric.dumazet@gmail.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: linux-net@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: error while building the kernel Mainline
Date: Thu, 18 Nov 2010 16:12:15 +0100 [thread overview]
Message-ID: <1290093135.2781.167.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTikToBjx-4go9mAFCcnTQ5X4Su+57ODoY9C5y_7f@mail.gmail.com>
Le jeudi 18 novembre 2010 à 06:36 -0800, Justin Mattock a écrit :
> hit this yesterday, and havent had time to look at it, to see if its a
> simple fix
>
> MODPOST vmlinux.o
> WARNING: modpost: Found 1 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> GEN .version
> CHK include/generated/compile.h
> UPD include/generated/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> net/built-in.o: In function `handle_response_icmp':
> ip_vs_core.c:(.text+0x2b5c4): undefined reference to `nf_conntrack_untracked'
> net/built-in.o: In function `T.925':
> ip_vs_core.c:(.text+0x2cbbd): undefined reference to `nf_conntrack_untracked'
> net/built-in.o: In function `ip_vs_null_xmit':
> (.text+0x310da): undefined reference to `nf_conntrack_untracked'
> net/built-in.o: In function `ip_vs_tunnel_xmit':
> (.text+0x311e3): undefined reference to `nf_conntrack_untracked'
> net/built-in.o: In function `ip_vs_nat_xmit':
> (.text+0x3176f): undefined reference to `nf_conntrack_untracked'
> net/built-in.o:(.text+0x3199d): more undefined references to
> `nf_conntrack_untracked' follow
> make: *** [.tmp_vmlinux1] Error 1
>
> has there been anything sent forward for this yet?
>
Try to find out why net/netfilter/nf_conntrack_core.c is not compiled ?
./net/netfilter/nf_conntrack_core.c:65:DEFINE_PER_CPU(struct nf_conn, nf_conntrack_untracked);
./net/netfilter/nf_conntrack_core.c:66:EXPORT_PER_CPU_SYMBOL(nf_conntrack_untracked);
next prev parent reply other threads:[~2010-11-18 15:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 14:36 Justin Mattock
2010-11-18 15:12 ` Eric Dumazet [this message]
2010-11-18 17:25 ` Justin P. Mattock
2010-11-18 17:48 ` Eric Dumazet
2010-11-18 17:50 ` David Miller
2010-11-18 18:12 ` Patrick McHardy
2010-11-18 18:13 ` Justin P. Mattock
2010-11-18 18:20 ` Patrick McHardy
2010-11-18 18:28 ` Justin P. Mattock
2010-11-18 19:18 ` Justin P. Mattock
2010-11-18 20:32 ` Patrick McHardy
2010-11-18 20:54 ` David Miller
2010-11-18 21:03 ` Randy Dunlap
2010-11-18 21:10 ` David Miller
2010-11-18 21:15 ` David Miller
2010-11-18 21:48 ` Patrick McHardy
2010-11-18 23:48 ` Justin P. Mattock
2010-11-19 0:20 ` Simon Horman
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=1290093135.2781.167.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.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 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®