Re: GPGME 1.23.1

Denis Corbin <[email protected]> Mon, 6 Nov 2023 21:49:27 +0100
Newsgroups gmane.comp.sysutils.backup.dar.support
Message-ID <[email protected]>
On 06/11/2023 10:05, Marcin Wieczorek wrote:
> 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

I was wrong, there is a version check also in the configure script for 
gpgme. This comes with the AM_PATH_GPGME macro used in dar/libdar 
configure.ac file.

The "WARNING:*" line shows because the macro did not pass.

I'd be interested in the following output:

	grep GPGME config.log

Could you check also you do not have an old gpgme.h header file 
somewhere? This should help.
	
	find /usr -type f -name "gpgme.h" -ls

Last track, you can add the --with-gpgme-prefix=PFX option to configure
to force the path to where gpgme has been installed: For example:

	./configure --with-gpgme-prefix=/usr/local  ... other options...


> #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

Interesting...

Well, if there is one AC_CHECK_LIB for gpgme in the dar's configure.ac 
file, it comes in consideration only once and if AM_PATH_GPGME 
succeeded, and in no case its failure is problematic. Not likely to be 
the same problem here as the bug report you mentioned.

However the report underlines that the AM_PATH_GPGME relies on 
gpgme-config utility. Do you have it in your PATH?

if so, what's the output of

	gpgme-config --version

and

	gpgme-config --print-lang


> 
>> 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.*

OK, thanks for the info.

> 
> Best regards,
> Marcin Wieczorek
> 
> 

Cheers,
Denis
OpenPGP_signature.asc (application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEVeSEpqXFvH9T9/cuqLFBYNNrO6cFAmVJUVcFAwAAAAAACgkQqLFBYNNrO6dD
Uw//TtVhE7qjmsiePjdDlEb+iQmO+BvFk21I1KgSCAOMNcOxDMGGHpS9RsARviaEdC5MliUo36Dm
aXTEwlzrd6wrZ3c7oTf0uNguFevYhAousZo7I5oNu72D8npwGwmwoXTkb4j046H/NqP3Qk4RJ2QB
jIn4J4H/+bCBOzgLAewaGvWNtyWezsOSaKHZGcEsI8dMeynvbZY0VGN9YV9bMWSPpbVmOE/nT1zw
VwPHHTBQ1RVGPFthz1tn6nkf1PbnUM6TqRljLAX7kWltMr/ekZJYhIfs6hBG1EEfy9z+YFS1R+sr
I2DHTeo/OOCohM2+vLjkbIkI47RQ8GPZNs9+3h9r2bSvKjO+i45QvMmZRp/itL/TE4+CruR/17M+
hRZAuesS/48Y4EdonpcvgDmsdtzOg9yueRaixdt2fBcY1K3Nrq8k9NEf8eOVMqji0tTGNPceakUw
YfysGrgDA6/k1GjZX6skoreS6C5Aebp2RSE/Jef1JrqB5VmgUuMkRJrxx2TPiWj7QImqcsbi/l01
Fj99Fic3mxdn8dGP+8ZHSpasv5v4ukweEaccse5kdQhkCTRyoSwWz71Izcxn5z/vZDpYsxhezAj8
o+2tWq82TrRQJu6UpKvBVEVDtvlJmCGN168uPOZUSNH/D/cq3BqI9mbWq3xzW1M1BtDKnpzJPrIE
1SA=
=TZPB
-----END PGP SIGNATURE-----