Mailing List Archive: GnuPG: devel

building gpgme for Android dies on install

Index | Next | Previous | View Threaded

hans at guardianproject

Aug 15, 2012, 2:38 PM

Post #1 of 9 (227 views)
Permalink

building gpgme for Android dies on install

Hey all,

I'm back at it, this time trying to get gpgme and gnupg-for-java all
working on Android. gpgme is quite close, there seems to be only an
error on the install. I'm building 1.3.2 using the Android NDK r8b.

The good news is that I no longer need to patch gpgme to build it, nor
update config.guess and config.sub. Thanks! :) You can see the
./configure flags used here, and indeed the whole build setup:
https://github.com/guardianproject/gnupg-for-android/blob/master/external/Makefile#L557

Now for the install error (I've never heard of a .lai file...). Its
trying to install libgpgme.lai as libgpgme.la, but libgpgme.lai doesn't
exist. src/libgpgme.la does tho.

Here's the full log:

$ make -C gpgme
DESTDIR=/media/share/code/guardianproject/gnupg-for-android/external/../external
prefix=/data/data/info.guardianproject.gpg/app_opt install
make: Entering directory
`/media/share/code/guardianproject/gnupg-for-android/external/gpgme'
Making install in src
make[1]: Entering directory
`/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
make[2]: Entering directory
`/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
test -z "/data/data/info.guardianproject.gpg/app_opt/bin" || /bin/mkdir
-p
"/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/bin"
/usr/bin/install -c gpgme-config
'/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/bin'
test -z "/data/data/info.guardianproject.gpg/app_opt/lib" || /bin/mkdir
-p
"/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib"
/bin/bash ../libtool --mode=install /usr/bin/install -c libgpgme.la
'/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib'
libtool: install: /usr/bin/install -c .libs/libgpgme.so.11.8.1
/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib/libgpgme.so.11.8.1
libtool: install: (cd
/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib
&& { ln -s -f libgpgme.so.11.8.1 libgpgme.so.11 || { rm -f
libgpgme.so.11 && ln -s libgpgme.so.11.8.1 libgpgme.so.11; }; })
libtool: install: (cd
/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib
&& { ln -s -f libgpgme.so.11.8.1 libgpgme.so || { rm -f libgpgme.so &&
ln -s libgpgme.so.11.8.1 libgpgme.so; }; })
libtool: install: /usr/bin/install -c .libs/libgpgme.lai
/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib/libgpgme.la
/usr/bin/install: cannot stat `.libs/libgpgme.lai': No such file or
directory
make[2]: *** [install-libLTLIBRARIES] Error 1
make[2]: Leaving directory
`/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory
`/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
make: *** [install-recursive] Error 1
make: Leaving directory
`/media/share/code/guardianproject/gnupg-for-android/external/gpgme'

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

hans at guardianproject

Aug 15, 2012, 5:48 PM

Post #2 of 9 (205 views)
Permalink

Re: building gpgme for Android dies on install [In reply to]

I found a clue. It seems that the first time when running the
gpgme-install, it fails with a different error, then every time after,
it gives the error below. Here's the first time error:

/bin/sed: can't read
/data/data/info.guardianproject.gpg/app_opt/lib/libgpg-error.la: No such
file or directory
libtool: link:
`/data/data/info.guardianproject.gpg/app_opt/lib/libgpg-error.la' is not
a valid libtool archive
make[3]: *** [libgpgme.la] Error 1
make[3]: Leaving directory
`/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/media/share/code/guardianproject/gnupg-for-android/external/gpgme'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/media/share/code/guardianproject/gnupg-for-android/external/gpgme'

And some relevant info:

* since this is a cross-compile, the various libs like libgpg-error
can't be meaningfully installed before compiling gpgme. So there is
a sed hack to change the *-config scripts to point to the right
things to get stuff building:

sed -i 's|^prefix=$(prefix)|prefix=$(LOCAL)|' $(LOCAL)/bin/*-config

* prefix=/data/data/info.guardianproject.gpg/app_opt

* libgpg-error.la exists at $(DESTDIR)$(prefix)/lib/libgpg-error.la

Still hunting around... I found a new debug trick which is helping:

make SHELL="/bin/bash -vx" install

.hc

On 08/15/2012 05:38 PM, Hans-Christoph Steiner wrote:
>
> Hey all,
>
> I'm back at it, this time trying to get gpgme and gnupg-for-java all
> working on Android. gpgme is quite close, there seems to be only an
> error on the install. I'm building 1.3.2 using the Android NDK r8b.
>
> The good news is that I no longer need to patch gpgme to build it, nor
> update config.guess and config.sub. Thanks! :) You can see the
> ./configure flags used here, and indeed the whole build setup:
> https://github.com/guardianproject/gnupg-for-android/blob/master/external/Makefile#L557
>
> Now for the install error (I've never heard of a .lai file...). Its
> trying to install libgpgme.lai as libgpgme.la, but libgpgme.lai doesn't
> exist. src/libgpgme.la does tho.
>
> Here's the full log:
>
> $ make -C gpgme
> DESTDIR=/media/share/code/guardianproject/gnupg-for-android/external/../external
> prefix=/data/data/info.guardianproject.gpg/app_opt install
> make: Entering directory
> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme'
> Making install in src
> make[1]: Entering directory
> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
> make[2]: Entering directory
> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
> test -z "/data/data/info.guardianproject.gpg/app_opt/bin" || /bin/mkdir
> -p
> "/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/bin"
> /usr/bin/install -c gpgme-config
> '/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/bin'
> test -z "/data/data/info.guardianproject.gpg/app_opt/lib" || /bin/mkdir
> -p
> "/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib"
> /bin/bash ../libtool --mode=install /usr/bin/install -c libgpgme.la
> '/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib'
> libtool: install: /usr/bin/install -c .libs/libgpgme.so.11.8.1
> /media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib/libgpgme.so.11.8.1
> libtool: install: (cd
> /media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib
> && { ln -s -f libgpgme.so.11.8.1 libgpgme.so.11 || { rm -f
> libgpgme.so.11 && ln -s libgpgme.so.11.8.1 libgpgme.so.11; }; })
> libtool: install: (cd
> /media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib
> && { ln -s -f libgpgme.so.11.8.1 libgpgme.so || { rm -f libgpgme.so &&
> ln -s libgpgme.so.11.8.1 libgpgme.so; }; })
> libtool: install: /usr/bin/install -c .libs/libgpgme.lai
> /media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib/libgpgme.la
> /usr/bin/install: cannot stat `.libs/libgpgme.lai': No such file or
> directory
> make[2]: *** [install-libLTLIBRARIES] Error 1
> make[2]: Leaving directory
> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
> make[1]: *** [install-am] Error 2
> make[1]: Leaving directory
> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
> make: *** [install-recursive] Error 1
> make: Leaving directory
> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme'
>

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

hans at guardianproject

Aug 15, 2012, 6:35 PM

Post #3 of 9 (211 views)
Permalink

Re: building gpgme for Android dies on install [In reply to]

I believe I found the source of the trouble. The various *-config
scripts all return values based on the assumption that everything will
be installed before being used. Since we're cross-compiling, that's not
the case.

So now I'm trying to force things by using sed to replace prefix= in the
various *-config scripts, but I haven't find a good time in the process
to do that, and a good pattern to guarantee the results needed...

.hc

On 08/15/2012 08:48 PM, Hans-Christoph Steiner wrote:
>
> I found a clue. It seems that the first time when running the
> gpgme-install, it fails with a different error, then every time after,
> it gives the error below. Here's the first time error:
>
> /bin/sed: can't read
> /data/data/info.guardianproject.gpg/app_opt/lib/libgpg-error.la: No such
> file or directory
> libtool: link:
> `/data/data/info.guardianproject.gpg/app_opt/lib/libgpg-error.la' is not
> a valid libtool archive
> make[3]: *** [libgpgme.la] Error 1
> make[3]: Leaving directory
> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory
> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory
> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme'
>
> And some relevant info:
>
> * since this is a cross-compile, the various libs like libgpg-error
> can't be meaningfully installed before compiling gpgme. So there is
> a sed hack to change the *-config scripts to point to the right
> things to get stuff building:
>
> sed -i 's|^prefix=$(prefix)|prefix=$(LOCAL)|' $(LOCAL)/bin/*-config
>
> * prefix=/data/data/info.guardianproject.gpg/app_opt
>
> * libgpg-error.la exists at $(DESTDIR)$(prefix)/lib/libgpg-error.la
>
> Still hunting around... I found a new debug trick which is helping:
>
> make SHELL="/bin/bash -vx" install
>
> .hc
>
> On 08/15/2012 05:38 PM, Hans-Christoph Steiner wrote:
>>
>> Hey all,
>>
>> I'm back at it, this time trying to get gpgme and gnupg-for-java all
>> working on Android. gpgme is quite close, there seems to be only an
>> error on the install. I'm building 1.3.2 using the Android NDK r8b.
>>
>> The good news is that I no longer need to patch gpgme to build it, nor
>> update config.guess and config.sub. Thanks! :) You can see the
>> ./configure flags used here, and indeed the whole build setup:
>> https://github.com/guardianproject/gnupg-for-android/blob/master/external/Makefile#L557
>>
>> Now for the install error (I've never heard of a .lai file...). Its
>> trying to install libgpgme.lai as libgpgme.la, but libgpgme.lai doesn't
>> exist. src/libgpgme.la does tho.
>>
>> Here's the full log:
>>
>> $ make -C gpgme
>> DESTDIR=/media/share/code/guardianproject/gnupg-for-android/external/../external
>> prefix=/data/data/info.guardianproject.gpg/app_opt install
>> make: Entering directory
>> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme'
>> Making install in src
>> make[1]: Entering directory
>> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
>> make[2]: Entering directory
>> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
>> test -z "/data/data/info.guardianproject.gpg/app_opt/bin" || /bin/mkdir
>> -p
>> "/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/bin"
>> /usr/bin/install -c gpgme-config
>> '/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/bin'
>> test -z "/data/data/info.guardianproject.gpg/app_opt/lib" || /bin/mkdir
>> -p
>> "/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib"
>> /bin/bash ../libtool --mode=install /usr/bin/install -c libgpgme.la
>> '/media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib'
>> libtool: install: /usr/bin/install -c .libs/libgpgme.so.11.8.1
>> /media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib/libgpgme.so.11.8.1
>> libtool: install: (cd
>> /media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib
>> && { ln -s -f libgpgme.so.11.8.1 libgpgme.so.11 || { rm -f
>> libgpgme.so.11 && ln -s libgpgme.so.11.8.1 libgpgme.so.11; }; })
>> libtool: install: (cd
>> /media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib
>> && { ln -s -f libgpgme.so.11.8.1 libgpgme.so || { rm -f libgpgme.so &&
>> ln -s libgpgme.so.11.8.1 libgpgme.so; }; })
>> libtool: install: /usr/bin/install -c .libs/libgpgme.lai
>> /media/share/code/guardianproject/gnupg-for-android/external/../external/data/data/info.guardianproject.gpg/app_opt/lib/libgpgme.la
>> /usr/bin/install: cannot stat `.libs/libgpgme.lai': No such file or
>> directory
>> make[2]: *** [install-libLTLIBRARIES] Error 1
>> make[2]: Leaving directory
>> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
>> make[1]: *** [install-am] Error 2
>> make[1]: Leaving directory
>> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme/src'
>> make: *** [install-recursive] Error 1
>> make: Leaving directory
>> `/media/share/code/guardianproject/gnupg-for-android/external/gpgme'
>>

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

wk at gnupg

Aug 16, 2012, 12:16 AM

Post #4 of 9 (205 views)
Permalink

Re: building gpgme for Android dies on install [In reply to]

On Thu, 16 Aug 2012 02:48, hans [at] guardianproject said:

> * since this is a cross-compile, the various libs like libgpg-error
> can't be meaningfully installed before compiling gpgme. So there is
> a sed hack to change the *-config scripts to point to the right
> things to get stuff building:

That is not good. Install them please and provide the --with-foo-prefix
options. Check how we do this in autogen.sh for Windows; Given that
Android is a common platform, it makes sense to add support for it to
autogen.sh.

Shalom-Salam,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

marcus.brinkmann at ruhr-uni-bochum

Aug 16, 2012, 12:31 AM

Post #5 of 9 (205 views)
Permalink

Re: building gpgme for Android dies on install [In reply to]

On 08/16/2012 03:35 AM, Hans-Christoph Steiner wrote:
>
> I believe I found the source of the trouble. The various *-config
> scripts all return values based on the assumption that everything will
> be installed before being used. Since we're cross-compiling, that's not
> the case.

pkgconfig and its imitations (such as our config scripts) share this
problem with libtool.

> So now I'm trying to force things by using sed to replace prefix= in the
> various *-config scripts, but I haven't find a good time in the process
> to do that, and a good pattern to guarantee the results needed...

Don't forget the .la files :) That's actually the canonical way to do
it, I think (and yes, it's a PITA). For GPGME and friends, you can also
just build and install for the cross-compilation build paths, and
use the --with-gpg and --with-gpgsm etc. options to specify the
hard-coded target file names of the crypto engines. The result is
relocatable except for the .la and -config files, which need to be fixed
up anyway. (So, if you want to develop on build and target, you
absolutely need two copies of those files, no matter what you do).

Thanks,
Marcus

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

wk at gnupg

Aug 16, 2012, 2:02 AM

Post #6 of 9 (205 views)
Permalink

Re: building gpgme for Android dies on install [In reply to]

On Thu, 16 Aug 2012 09:31, marcus.brinkmann [at] ruhr-uni-bochum said:

> pkgconfig and its imitations (such as our config scripts) share this
> problem with libtool.

FWIW, last week we had a long discussion on it at
gnu-prog-dicuss [at] gnu Unfortunately that list is - for stupid
reasons - secret and should only be known to GNU maintainers. Thus I
fear any such discussion has to be repeated on a public list.

Salam-Shalom,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

hans at guardianproject

Aug 16, 2012, 11:36 AM

Post #7 of 9 (204 views)
Permalink

Re: building gpgme for Android dies on install [In reply to]

On 08/16/2012 03:31 AM, Marcus Brinkmann wrote:
> On 08/16/2012 03:35 AM, Hans-Christoph Steiner wrote:
>>
>> I believe I found the source of the trouble. The various *-config
>> scripts all return values based on the assumption that everything will
>> be installed before being used. Since we're cross-compiling, that's not
>> the case.
>
> pkgconfig and its imitations (such as our config scripts) share this
> problem with libtool.
>
>> So now I'm trying to force things by using sed to replace prefix= in the
>> various *-config scripts, but I haven't find a good time in the process
>> to do that, and a good pattern to guarantee the results needed...
>
> Don't forget the .la files :) That's actually the canonical way to do
> it, I think (and yes, it's a PITA). For GPGME and friends, you can also
> just build and install for the cross-compilation build paths, and
> use the --with-gpg and --with-gpgsm etc. options to specify the
> hard-coded target file names of the crypto engines. The result is
> relocatable except for the .la and -config files, which need to be fixed
> up anyway. (So, if you want to develop on build and target, you
> absolutely need two copies of those files, no matter what you do).

Ah yes! That was the trick to get everything to build. I set --prefix=
on all of the libs to what I had been using for $(DESTDIR)$(prefix) and
the whole build worked. I'll test it now. The only question I have is
that setting --prefix= in gnupg will alter where gpg-agent puts its
socket file, no?

.hc

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

hans at guardianproject

Aug 16, 2012, 4:58 PM

Post #8 of 9 (202 views)
Permalink

Re: building gpgme for Android dies on install [In reply to]

On 08/16/2012 02:36 PM, Hans-Christoph Steiner wrote:
>
> On 08/16/2012 03:31 AM, Marcus Brinkmann wrote:
>> On 08/16/2012 03:35 AM, Hans-Christoph Steiner wrote:
>>>
>>> I believe I found the source of the trouble. The various *-config
>>> scripts all return values based on the assumption that everything will
>>> be installed before being used. Since we're cross-compiling, that's not
>>> the case.
>>
>> pkgconfig and its imitations (such as our config scripts) share this
>> problem with libtool.
>>
>>> So now I'm trying to force things by using sed to replace prefix= in the
>>> various *-config scripts, but I haven't find a good time in the process
>>> to do that, and a good pattern to guarantee the results needed...
>>
>> Don't forget the .la files :) That's actually the canonical way to do
>> it, I think (and yes, it's a PITA). For GPGME and friends, you can also
>> just build and install for the cross-compilation build paths, and
>> use the --with-gpg and --with-gpgsm etc. options to specify the
>> hard-coded target file names of the crypto engines. The result is
>> relocatable except for the .la and -config files, which need to be fixed
>> up anyway. (So, if you want to develop on build and target, you
>> absolutely need two copies of those files, no matter what you do).
>
> Ah yes! That was the trick to get everything to build. I set --prefix=
> on all of the libs to what I had been using for $(DESTDIR)$(prefix) and
> the whole build worked. I'll test it now. The only question I have is
> that setting --prefix= in gnupg will alter where gpg-agent puts its
> socket file, no?

And changing prefix= to the whole thing on 'gnupg' means it looks in the
wrong place for dirmngr and friends. Looks like I'll need a sed hack
after all.

.hc

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

hans at guardianproject

Aug 16, 2012, 8:58 PM

Post #9 of 9 (209 views)
Permalink

Re: building gpgme for Android dies on install [In reply to]

On 08/16/2012 07:58 PM, Hans-Christoph Steiner wrote:
>
>
> On 08/16/2012 02:36 PM, Hans-Christoph Steiner wrote:
>>
>> On 08/16/2012 03:31 AM, Marcus Brinkmann wrote:
>>> On 08/16/2012 03:35 AM, Hans-Christoph Steiner wrote:
>>>>
>>>> I believe I found the source of the trouble. The various *-config
>>>> scripts all return values based on the assumption that everything will
>>>> be installed before being used. Since we're cross-compiling, that's not
>>>> the case.
>>>
>>> pkgconfig and its imitations (such as our config scripts) share this
>>> problem with libtool.
>>>
>>>> So now I'm trying to force things by using sed to replace prefix= in the
>>>> various *-config scripts, but I haven't find a good time in the process
>>>> to do that, and a good pattern to guarantee the results needed...
>>>
>>> Don't forget the .la files :) That's actually the canonical way to do
>>> it, I think (and yes, it's a PITA). For GPGME and friends, you can also
>>> just build and install for the cross-compilation build paths, and
>>> use the --with-gpg and --with-gpgsm etc. options to specify the
>>> hard-coded target file names of the crypto engines. The result is
>>> relocatable except for the .la and -config files, which need to be fixed
>>> up anyway. (So, if you want to develop on build and target, you
>>> absolutely need two copies of those files, no matter what you do).
>>
>> Ah yes! That was the trick to get everything to build. I set --prefix=
>> on all of the libs to what I had been using for $(DESTDIR)$(prefix) and
>> the whole build worked. I'll test it now. The only question I have is
>> that setting --prefix= in gnupg will alter where gpg-agent puts its
>> socket file, no?
>
> And changing prefix= to the whole thing on 'gnupg' means it looks in the
> wrong place for dirmngr and friends. Looks like I'll need a sed hack
> after all.

Ok, I think I got the right combo of prefix and DESTDIR, and then
setting the paths to the various tools. Now I'm stuck with an "Invalid
crypto engine" exception from gpgme even tho the path to the gpg2 that
it has is correct, and gpg2 seems to work in the Android terminal.

.hc

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads