Re: GPGME 1.23.1

Marcin Wieczorek <[email protected]> Mon, 6 Nov 2023 10:05:28 +0100

Newsgroups	gmane.comp.sysutils.backup.dar.support
Message-ID	<gx6nb44nf26ads6rsautrns5n4g342wgwptmqjqvvdie2i6yan@feehpuogmrdz>

Thank you for your reply.

> you should find in the config.log file generated by the configure script the
> reason why the configure script failed to activate public key cipher
> support.

config.log doesn't say anything useful.

configure:26197: checking for gpgme-config
configure:26228: result: no
configure:26276: checking for GPGME - version >= 1.2.0
configure:26462: result: no
configure:26464: WARNING: Public key support (GPGME linking) requires version greater than 1.2.0
#define HAVE_LIBGPG_ERROR 1

I read that gpgme-config has been deprecated. I think it would be used
to determine the version if present.

Also see: https://bugs.archlinux.org/task/26495

> Sure. Double check you have all the prerequisites here:
> 
> http://dar.linux.free.fr/doc/from_sources.html

I have both libgcrypt and libgpgme which are required for strong
asymmetric encryption. I obviously have required packages such as a
compiler, linker and make.

> 
> For libraries, you should have installed also the included files. Debian
> makes sperarated packages for them, those ending with *-dev, don't know
> about Arch. Anyway, this should show in the config.log generated file

Arch includes headers in packages, there are no -dev pkgs.

Best regards,
Marcin Wieczorek

signature.asc (application/pgp-signature, 488 B)