Quite a few of the new sparc64 failures are related to neon:
> http://build-failures.rhaalovely.net/sparc64/2022-01-03/audio/libmusicbrainz.log
> http://build-failures.rhaalovely.net/sparc64/2022-01-03/audio/libmusicbrainz5.log
/usr/local/lib/libneon.so.31.3: undefined reference to `EVP_sha512_256'
This can be replicated on amd64 with USE_LLD=No
Presumably this in src/ne_openssl.c:
...
| static const EVP_MD *hash_to_md(unsigned int flags)
| {
| switch (flags & NE_HASH_ALGMASK) {
| case NE_HASH_MD5: return EVP_md5();
| case NE_HASH_SHA256: return EVP_sha256();
| #ifdef HAVE_OPENSSL11
| case NE_HASH_SHA512: return EVP_sha512();
| case NE_HASH_SHA512_256: return EVP_sha512_256();
| #endif
...
The others aren't explicit but I guess quite likely to have the same cause:
> http://build-failures.rhaalovely.net/sparc64/2022-01-03/net/cadaver.log
configure: incompatible neon library version 0.32.1: wanted 0.27 28 29 30 31 32
> http://build-failures.rhaalovely.net/sparc64/2022-01-03/telephony/asterisk/16.log
> http://build-failures.rhaalovely.net/sparc64/2022-01-03/telephony/asterisk/18.log
> http://build-failures.rhaalovely.net/sparc64/2022-01-03/telephony/asterisk/19.log
not clear from the build log but the module which isn't built depends on neon;
config.log and/or menuselect-generated files probably tell more
> http://build-failures.rhaalovely.net/sparc64/2022-01-03/sysutils/nut.log
"checking whether to build neon based XML driver... no"
config.log probably tells more
