Jeffrey Walton noloader@gmail.com writes:

And it looks like examples are not quite working either:

$ make check ... ==================== All 110 tests passed ==================== Making check in examples TEST_SHLIB_DIR="/Users/jwalton/Build-Scripts/nettle-3.7.2/.lib" \ srcdir="." EMULATOR="" EXEEXT="" \ ".."/run-tests rsa-sign-test rsa-verify-test rsa-encrypt-test Opening `testkey' failed: No such file or directory Invalid key FAIL: rsa-sign Opening `testkey' failed: No such file or directory Invalid key FAIL: rsa-verify Opening `testkey.pub' failed: No such file or directory Invalid key FAIL: rsa-encrypt =================== 3 of 3 tests failed =================== make[1]: *** [check] Error 1 make: *** [check] Error 2

$ find . -name testkey.pub $ find . -name testkey

My best guess is that your operating system fails to regard the scripts examples/setup-env and teardown-env as executable (similarly to the main run-tests script). The setup-env script is supposed to create those files.

The executability-bit that is set on certain files in the tarball must be honored for the build to work correctly. Please to whatever it takes to convince your build environment to do that.

Examples have been breaking the build for years. Why are examples even built during 'make check'?

The tests that are failing for you act as a kind of integration-level test for the library. I think that has some value.

Regards, /Niels