Suggested by @theuni
Unneeded and was causing travis issues downstream.
Suggested by @theuni
Unneeded and was causing travis issues downstream.
utACK. @instagibbs had an unrelated build failure due to (auto) jni detection in libsecp256k1. Regardless of that problem (which should be addressed), we should be deterministic in the downstream features we enable/build.
What is jni and how would it possibly have any influence on us?
libsecp256k1 has (optional) JNI bindings
utACK 844b73e486ca146f3f9f3060e878814752c25fd5 though I think the libsecp256k1 JNI (java native interface) default should not be auto ("no" as default makes more sense IMO).
If the answer is that it doesn't affect us in any way, then it should be disabled, I agree. If anything it's a waste of resources building.
utACK.