From: Patrick McHardy <kaber@trash.net>
To: Pete Clements <clem@clem.clem-digital.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: 2.6.25-git2 fails build (nf_nat_proto_sctp.ko)
Date: Sat, 19 Apr 2008 19:10:38 +0200 [thread overview]
Message-ID: <480A278E.60507@trash.net> (raw)
In-Reply-To: <200804191329.m3JDTS0m023459@clem.clem-digital.net>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
Pete Clements wrote:
> Root device is (3, 1)
> Setup is 11288 bytes (padded to 11776 bytes).
> System is 1162 kB
> CRC 695701be
> Kernel: arch/x86/boot/bzImage is ready (#4)
> Building modules, stage 2.
> MODPOST 132 modules
> ERROR: "crc32c_le" [net/ipv4/netfilter/nf_nat_proto_sctp.ko] undefined!
Sorry about that. We need to select LIBCRC32C.
Signed-off-by: Patrick McHardy <kaber@trash.net>
[-- Attachment #2: x --]
[-- Type: text/plain, Size: 349 bytes --]
diff --git a/net/ipv4/netfilter/Kconfig b/net/ipv4/netfilter/Kconfig
index 0c95cd5..2767841 100644
--- a/net/ipv4/netfilter/Kconfig
+++ b/net/ipv4/netfilter/Kconfig
@@ -259,6 +259,7 @@ config NF_NAT_PROTO_SCTP
tristate
default NF_NAT && NF_CT_PROTO_SCTP
depends on NF_NAT && NF_CT_PROTO_SCTP
+ select LIBCRC32C
config NF_NAT_FTP
tristate
next parent reply other threads:[~2008-04-19 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804191329.m3JDTS0m023459@clem.clem-digital.net>
2008-04-19 17:10 ` Patrick McHardy [this message]
2008-04-20 0:52 ` 2.6.25-git2 fails build (nf_nat_proto_sctp.ko) David Miller
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=480A278E.60507@trash.net \
--to=kaber@trash.net \
--cc=clem@clem.clem-digital.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).