THE CODE COMPILES
=============
My Rpi 5 and Opi 5 units, also my Rpi 4, have all successfully compiled v24.1. I used the "ARMv8" build script after finding a hint in the above reply. The "necessary packages" may have been missing.
After using your very latest prerequisite string, the build went to completion. The executable worked on each unit, printing out help.txt and Version info in each case. But, the Rpi 4 errored out when attempting to mine YescriptR16, likely due to its incomplete set of crypto instructions. It is currently mining Zephyr with XMRIG 6.20, slowly.
The Rpi 5 mines Verus at about 4850kH/s, the Opi 5 units at about 6800kH/s. They are using Oink's ccminer. I also have some older CPUs mining Verus with Monk's ccminer.
Perhaps you should look into a CCminer-Opt branch? A fine tune may really improve performance. Monk's version gets a lot of rejects at times. --scryptr
Thanks for the update. I'd lke to see the errors on RPi4. Is it only yescryptr16 that fails? Is it an error or crash? Are you building with -march=native or -march=armv8? Native is usually preferred
unless the CPU isn't known to the compiler.
Another note, CPU feature reporting isn't working on ARM but SW features are. If you build with -march=native the SW features should match the CPU's actual features,
except that I haven't yet figured out how to detect the ARM minor version, so you only see armv8, not armv8.N.
I'm not looking at adding Verus. There's no code resuse with cpuminer so it would be adding bloat. Oink's version is already optimized so I probably wouldn't be able to improve it.