GPGME 0.4.1 -- compile hassles

Bernhard Reiter bernhard at
Tue Jul 22 16:39:01 CEST 2003

On Tue, Jul 22, 2003 at 01:58:12PM +0200, Marcus Brinkmann wrote:
> On Thu, Jul 17, 2003 at 09:48:15PM +0200, Bernhard Reiter wrote:

> Ok.  Is it fixed in CVS now?
> Right.  I fixed that now in CVS (hopefully).

Thanks for the answer.
Note: I probably won't be able to test CVS in the near future.

> > 	Fixing the hassles above all 15 tests fails with:
> > 	t-encrypt.c:42: GPGME: Invalid crypto engine
> It works just fine for me, of course.  So maybe there is a problem with your
> configuration?  What is your GnuPG version?  1.2.2 is required.

With 1.2.3rc1 all tests passed fine.

The configuration output had confused me.
It told me the path to gnupg and a minimum version number,
so I was surprise that it did not check the minimum version number
of that found executable.
Wouldn't that we a good idea to check for the minium version
number for gpg and gpgsm and issue a warning in the configuration step?

> > ps.: Please cc: me on relevant replies, I'm not subscribed to gnupg-devel at .
> Mmh, maybe fix your Mail-Followup-To then :)

Many people don't pay attentions to the mail-followup-to,
thus I'd rather make it double sure.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : /pipermail/attachments/20030722/9c0ad0e7/attachment.bin

More information about the Gnupg-devel mailing list