From: sean <seandarcy2@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: git3 build dies at net/built-in.o: undefined __nfa_fill
Date: Sun, 18 Sep 2005 20:29:30 -0400 [thread overview]
Message-ID: <dgl0pa$75d$1@sea.gmane.org> (raw)
In-Reply-To: <dgkqhs$qt0$1@sea.gmane.org>
sean wrote:
> Jiri Slaby wrote:
>
>> sean napsal(a):
>>
>>> On amd64, gcc-4.0.1:
>>>
>>> .....
>>> GEN .version
>>> CHK include/linux/compile.h
>>> UPD include/linux/compile.h
>>> CC init/version.o
>>> LD init/built-in.o
>>> LD .tmp_vmlinux1
>>> net/built-in.o: In function `ip_ct_port_tuple_to_nfattr':
>>> : undefined reference to `__nfa_fill'
>
> .............
>
>>
>> .config needed
>> NETFILTER_NETLINK is not selected, maybe.
>>
>
> Nope.
>
> grep NETFILTER .config
> CONFIG_NETFILTER=y
> # CONFIG_NETFILTER_DEBUG is not set
> CONFIG_NETFILTER_NETLINK=m
> CONFIG_NETFILTER_NETLINK_QUEUE=m
> CONFIG_NETFILTER_NETLINK_LOG=m
>
> sean
>
But this built -n rc1-git4:
grep NETLINK .config
# CONFIG_IP_NF_CONNTRACK_NETLINK is not set
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
# CONFIG_NETFILTER_NETLINK_LOG is not set
???
ean
prev parent reply other threads:[~2005-09-19 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 0:50 git3 build dies at net/built-in.o: undefined __nfa_fill sean
2005-09-17 12:59 ` Jiri Slaby
2005-09-18 22:43 ` sean
2005-09-19 0:29 ` sean [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='dgl0pa$75d$1@sea.gmane.org' \
--to=seandarcy2@gmail.com \
--cc=linux-kernel@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 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.