From: Jason Self <jason@bluehome.net>
To: stable@vger.kernel.org
Subject: Re: Build error on openrisc with CONFIG_CRYPTO_LIB_CURVE25519
Date: Fri, 10 Jun 2022 18:25:23 -0700 [thread overview]
Message-ID: <20220610182523.2f5620a2@valencia> (raw)
In-Reply-To: <YqLTecx7MGFPOvhw@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Fri, 10 Jun 2022 07:15:37 +0200
Greg KH <greg@kroah.com> wrote:
> On Thu, Jun 09, 2022 at 04:29:43PM -0700, Jason Self wrote:
> > In building 5.15.46 & 5.10.121 with CRYPTO_LIB_CURVE25519=m I get
> > the following. My workaround is to leave it as
> > CRYPTO_LIB_CURVE25519=n for now.
> >
> > CONFIG_OR1K_1200=y
> > CONFIG_OPENRISC_BUILTIN_DTB="or1ksim"
> >
> > sed 's/\.ko$/\.o/' modules.order | scripts/mod/modpost -o
> > modules-only.symvers -i vmlinux.symvers -T - ERROR: modpost:
> > "__crypto_memneq" [lib/crypto/libcurve25519.ko] undefined!
> > make[1]: *** [scripts/Makefile.modpost:134: modules-only.symvers]
> > Error 1 make[1]: *** Deleting file 'modules-only.symvers' make:
> > *** [Makefile:1783: modules] Error 2
>
>
> Is this a new problem, or has it always been there for these kernel
> trees?
It's new; it began in 5.15.45 & 5.10.120, which is when make
oldconfig first prompted about CONFIG_CRYPTO_LIB_CURVE25519.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-11 1:25 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 [this message]
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
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=20220610182523.2f5620a2@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 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.