Guido Vranken

Did you also install the headers? Can you try this? ```sh tar jxf boost_1_74_0.tar.bz2 cd boost_1_74_0/ CFLAGS="" CXXFLAGS="" ./bootstrap.sh CFLAGS="" CXXFLAGS="" ./b2 headers cp -R boost/ /usr/include/ ```

Thank you @stephentyrone . Do you know of any portable way to extract the relevant (eg. non-padding) number of bytes of a long double? Something like a ```sizeof()``` which returns...

Thanks but I was already testing these functions by compiling with `WOLFSSL_PUBLIC_ECC_ADD_DBL`. Off-topic but I'm currently fuzzing these different bignum configurations: https://github.com/guidovranken/cryptofuzz/blob/master/docs/wolfcrypt.md Anything I should add?

@dgarske @SparkiDev is there any difference between adding --enable-sp-asm and not? It seems that `wolfcrypt/src/sp_x86_64_asm.S` is compiled in both cases.

@jedisct1

> Is it fine to merge this despite the failures? Yes this + https://github.com/google/oss-fuzz/pull/11943 should make the projects succeed.

> I do not think we want new 1.1.1 specific targets. The 1.1.1 is security-fix only now The aim of fuzzing is to find security bugs so imho it makes...

I've created a PR here https://github.com/google/oss-fuzz/pull/8969 This builds all the fuzzers for master, 1.1.1 and 32 bit. Should I build @bernd-edlinger 's 111 feature branch instead? Any other changes I...

Ok. Should it have `openssl/OpenSSL_1_1_1-stable` AND `bernd-edlinger/openssl-111-features` or only the latter?

I've updated the PR. It now builds the following targets: Branches `[master, OpenSSL_1_1_1-stable, openssl-3.0]` x `[x64 ASAN, x64 UBSAN, x64 MSAN, i386 ASAN]` x `[individual fuzzers (client, server, x509, ...)]`...