On 6/11/22 08:25, Jason Self wrote: > On Fri, 10 Jun 2022 07:15:37 +0200 > Greg KH <greg@xxxxxxxxx> 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. What did you answer for that new config? -- An old man doll... just what I always wanted! - Clara
