From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Cc: David Howells <dhowells@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Vlad Yasevich <vladislav.yasevich@hp.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [build bug] SCTP, net/sctp/auth.c, ./net/rxrpc/ar-key.c fails to build
Date: Wed, 28 Nov 2007 13:47:30 +0100 [thread overview]
Message-ID: <20071128124730.GA19498@elte.hu> (raw)
In-Reply-To: <20071128124433.GA18378@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> a similar build bug happens with latest -git as well, with SCTP:
>
> net/built-in.o: In function `rxrpc_destroy_s':
> ar-key.c:(.text+0xc5a2b): undefined reference to `crypto_free_tfm'
> net/built-in.o: In function `rxrpc_instantiate_s':
> ar-key.c:(.text+0xc5ed9): undefined reference to `crypto_alloc_base'
> net/built-in.o: In function `sctp_endpoint_put':
> : undefined reference to `crypto_free_tfm'
> net/built-in.o: In function `sctp_inet_listen':
> : undefined reference to `crypto_free_tfm'
> net/built-in.o: In function `sctp_auth_destroy_hmacs':
> : undefined reference to `crypto_free_tfm'
> net/built-in.o: In function `sctp_auth_init_hmacs':
> : undefined reference to `crypto_alloc_base'
>
> this is a build regression over v2.6.23. config attached.
the patch below fix it (or rather, works it around).
Ingo
------------->
Subject: SCTP: fix build bug
From: Ingo Molnar <mingo@elte.hu>
fix build bug:
net/built-in.o: In function `rxrpc_destroy_s':
ar-key.c:(.text+0xc5a2b): undefined reference to `crypto_free_tfm'
net/built-in.o: In function `rxrpc_instantiate_s':
ar-key.c:(.text+0xc5ed9): undefined reference to `crypto_alloc_base'
net/built-in.o: In function `sctp_endpoint_put':
: undefined reference to `crypto_free_tfm'
net/built-in.o: In function `sctp_inet_listen':
: undefined reference to `crypto_free_tfm'
net/built-in.o: In function `sctp_auth_destroy_hmacs':
: undefined reference to `crypto_free_tfm'
net/built-in.o: In function `sctp_auth_init_hmacs':
: undefined reference to `crypto_alloc_base'
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
net/sctp/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/net/sctp/Kconfig
===================================================================
--- linux.orig/net/sctp/Kconfig
+++ linux/net/sctp/Kconfig
@@ -6,7 +6,7 @@ menuconfig IP_SCTP
tristate "The SCTP Protocol (EXPERIMENTAL)"
depends on INET && EXPERIMENTAL
depends on IPV6 || IPV6=n
- select CRYPTO if SCTP_HMAC_SHA1 || SCTP_HMAC_MD5
+ select CRYPTO
select CRYPTO_HMAC if SCTP_HMAC_SHA1 || SCTP_HMAC_MD5
select CRYPTO_SHA1 if SCTP_HMAC_SHA1
select CRYPTO_MD5 if SCTP_HMAC_MD5
next prev parent reply other threads:[~2007-11-28 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 15:33 [build bug] " Ingo Molnar
2007-11-22 19:01 ` David Howells
2007-11-28 12:44 ` [build bug] SCTP, net/sctp/auth.c, " Ingo Molnar
2007-11-28 12:47 ` Ingo Molnar [this message]
2007-11-28 15:24 ` Vlad Yasevich
2007-11-28 14:58 ` Ingo Molnar
2007-11-28 16:05 ` Vlad Yasevich
2007-11-28 14:53 ` [PATCH] AF_RXRPC: Configure crypto correctly for AF_RXRPC David Howells
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=20071128124730.GA19498@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=vladislav.yasevich@hp.com \
/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
Powered by JetHome