From: Jason Self <jason@bluehome.net>
To: stable@vger.kernel.org
Subject: Re: Build error on openrisc with CONFIG_CRYPTO_LIB_CURVE25519
Date: Sat, 11 Jun 2022 10:39:21 -0700 [thread overview]
Message-ID: <20220611103921.7b56a960@valencia> (raw)
In-Reply-To: <819bb33c-bb9a-1da8-395a-67c9f4da798e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
On Sat, 11 Jun 2022 14:29:53 +0700
Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> > It's new; it began in 5.15.45 & 5.10.120, which is when make
> > oldconfig first prompted about CONFIG_CRYPTO_LIB_CURVE25519.
>
> What did you answer for that new config?
Initially "m" but "y" also seems to not matter. With "y":
or1k-linux-ld: lib/crypto/curve25519-selftest.o: in function
`curve25519_selftest': curve25519-selftest.c:(.init.text+0x7c):
undefined reference to `__crypto_memneq'
curve25519-selftest.c:(.init.text+0x7c): relocation truncated to fit:
R_OR1K_INSN_REL_26 against undefined symbol `__crypto_memneq'
or1k-linux-ld: curve25519-selftest.c:(.init.text+0x110): undefined
reference to `__crypto_memneq'
curve25519-selftest.c:(.init.text+0x110): relocation truncated to
fit: R_OR1K_INSN_REL_26 against undefined symbol `__crypto_memneq'
or1k-linux-ld: curve25519-selftest.c:(.init.text+0x140): undefined
reference to `__crypto_memneq'
curve25519-selftest.c:(.init.text+0x140): relocation truncated to
fit: R_OR1K_INSN_REL_26 against undefined symbol `__crypto_memneq'
or1k-linux-ld: curve25519-selftest.c:(.init.text+0x188): undefined
reference to `__crypto_memneq'
curve25519-selftest.c:(.init.text+0x188): relocation truncated to
fit: R_OR1K_INSN_REL_26 against undefined symbol `__crypto_memneq'
make: *** [Makefile:1183: vmlinux] Error 1
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-06-11 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 23:29 Build error on openrisc with CONFIG_CRYPTO_LIB_CURVE25519 Jason Self
2022-06-10 5:15 ` Greg KH
2022-06-11 1:25 ` Jason Self
2022-06-11 1:42 ` Jason Self
2022-06-11 3:09 ` Eric Biggers
2022-06-11 7:13 ` Jason A. Donenfeld
2022-06-12 6:57 ` Herbert Xu
2022-06-12 8:16 ` Jason A. Donenfeld
2022-06-13 9:45 ` Herbert Xu
2022-06-13 10:13 ` Jason A. Donenfeld
2022-06-11 7:29 ` Bagas Sanjaya
2022-06-11 17:39 ` Jason Self [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=20220611103921.7b56a960@valencia \
--to=jason@bluehome.net \
--cc=stable@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