From: Wakko Warner <wakko@animx.eu.org>
To: linux-kernel@vger.kernel.org
Subject: 2.6.39 nfsd and crypto =n
Date: Fri, 3 Jun 2011 13:45:28 -0400 [thread overview]
Message-ID: <20110603174528.GA1368@animx.eu.org> (raw)
During compile, I received this:
ERROR: "crypto_destroy_tfm" [fs/nfsd/nfsd.ko] undefined!
ERROR: "crypto_alloc_base" [fs/nfsd/nfsd.ko] undefined!
.config nfsd options:
CONFIG_NFSD=m
# CONFIG_NFSD_DEPRECATED is not set
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
and crypto:
# CONFIG_CRYPTO is not set
making the following change fixes:
-# CONFIG_CRYPTO is not set
+CONFIG_CRYPTO=m
Should NFSD_V4 select CRYPTO? Should it select other things?
--
Microsoft has beaten Volkswagen's world record. Volkswagen only created 22
million bugs.
next reply other threads:[~2011-06-03 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 17:45 Wakko Warner [this message]
2011-06-06 18:22 ` [PATCH] nfsd: v4 support requires CRYPTO Randy Dunlap
2011-06-06 22:41 ` J. Bruce Fields
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=20110603174528.GA1368@animx.eu.org \
--to=wakko@animx.eu.org \
--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 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®