Re: GPGME 1.23.1

Marcin Wieczorek <[email protected]> Wed, 8 Nov 2023 10:54:18 +0100
Newsgroups	gmane.comp.sysutils.backup.dar.support
Message-ID	<3kgvzwdy34yy7spgbtpv5bqzwunku2nglibog2uza52ukgbcht@2bk33pghkxtk>
Thank you for being interested and keen to help.

> 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.
>=20
> The "WARNING:*" line shows because the macro did not pass.
>=20
> I'd be interested in the following output:
>=20
> 	grep GPGME config.log

configure:26276: checking for GPGME - version >=3D 1.2.0
configure:26464: WARNING: Public key support (GPGME linking) requires versi=
on greater than 1.2.0
| #define GPGME_MIN_VERSION "1.2.0"
ac_cv_path_GPGME_CONFIG=3Dno
GPGME_CFLAGS=3D''
GPGME_CONFIG=3D'no'
GPGME_LIBS=3D''
#define GPGME_MIN_VERSION "1.2.0"

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

One entry and it does belong to the package. My system is purely managed
by the package manager. It's easier to package a thing than to do "sudo
make install" and cry later :)

2246044     96 -rw-r--r--   1 root     root        96749 Oct 27 15:53 /usr/=
include/gpgme.h


>=20
> Last track, you can add the --with-gpgme-prefix=3DPFX option to configure
> to force the path to where gpgme has been installed: For example:
>=20
> 	./configure --with-gpgme-prefix=3D/usr/local  ... other options...

It broke even further. It clearly looks for gpgme-config.

checking for gpgme-config... /usr/local/bin/gpgme-config
=2E/configure: line 26240: /usr/local/bin/gpgme-config: No such file or dir=
ectory
checking for GPGME - version >=3D 1.2.0... ./configure: line 26286: test: :=
 integer expression expected
=2E/configure: line 26289: test: : integer expression expected
no
configure: WARNING: Public key support (GPGME linking) requires version gre=
ater than 1.2.0

> Well, if there is one AC_CHECK_LIB for gpgme in the dar's configure.ac fi=
le,
> 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.
>=20
> However the report underlines that the AM_PATH_GPGME relies on gpgme-conf=
ig
> utility. Do you have it in your PATH?

I do not have gpgme-config in path and no package provides it (checked
using "pkgfile" tool which shows which package would contain that file).
Could you please tell me how to replace it with gpgrt-config? It might
be a drop in replacement:=20
https://dev.gnupg.org/T5683 (leads to:)
https://dev.gnupg.org/T6204
gpg-error-config and gpgme-config are deprecated to prefer pkg-config (or g=
pgrt-config).

I have gpgrt-config in PATH.

Best regards,
Marcin Wieczorek
signature.asc (application/pgp-signature, 488 B)