gpgme "Locate engine names only at runtime and prefer GnuPG-2" commit break Android
Hans-Christoph Steiner
hans at guardianproject.info
Thu Feb 20 02:57:15 CET 2014
"Locate engine names only at runtime and prefer GnuPG-2"
02ba35c1b6a2cbb3361b2f2ad507c53564b2be0b breaks gpgme for Android:
Running gpgme/run-import --verbose pubkey-1.asc
run-import: file run-support.h line 133: <GPGME> Invalid crypto engine
Running gpgme/run-import --verbose pubdemo.asc
run-import: file run-support.h line 133: <GPGME> Invalid crypto engine
Running gpgme/run-import --verbose pubkey-1.asc
run-import: file run-support.h line 133: <GPGME> Invalid crypto engine
Running gpgme/run-keylist --verbose
run-keylist: file run-support.h line 133: <GPGME> Invalid crypto engine
Running gpgme/run-import --verbose seckey-1.asc
run-import: file run-support.h line 133: <GPGME> Invalid crypto engine
Running gpgme/run-import --verbose secdemo.asc
run-import: file run-support.h line 133: <GPGME> Invalid crypto engine
Running gpgme/run-keylist --verbose
run-keylist: file run-support.h line 133: <GPGME> Invalid crypto engine
Using env vars is not a feasible solution on Android. The hard-coded option
that existed worked well.
.hc
--
PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81
More information about the Gnupg-devel
mailing list