Two patches for cygwin build of 1.4.1rc2
quetschke at scytek.de
Tue Mar 8 00:52:56 CET 2005
>>--- gnupg-1.4.1rc2-orig/scripts/config.rpath 2004-07-27
> config.rpath is part of libtool and updated with an automake
> update. Please report to the libtool maintainers.
I thought so, OK.
>>-AM_CFLAGS = -DGNUPG_LIBEXECDIR="\"$(libexecdir)\""
>>+AM_CFLAGS = -DGNUPG_LIBEXECDIR="\"$(libexecdir):$(bindir)\""
> This does not work. GNUPG_LIBEXECDIR is intended to be a single
> directory name and not a search path.
Well, this works fine. See the gnupg 1.4.0 cygwin package. What
you propably mean is that it is not supposed to work. ;)
The set_exec_path(GNUPG_LIBEXECDIR,...) command in keyserver.c just
adds/replaces the given string (here: GNUPG_LIBEXECDIR) into the path
environment variable (that only contains the exec-path at that moment).
> Use the runtime option --exec-path to specify a search path
Sure, that works but is not user friendly. Also using
"exec-path /bin" in gpg.conf works but also is not user friendly.
> or even better make sure to
> install the helpers in the correct directory.
They are, the problem is not finding the helper, but the helper needs
to find cygwin1.dll, therfore the need for /bin.
PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 254 bytes
Desc: OpenPGP digital signature
Url : /pipermail/attachments/20050307/5f774185/signature.pgp
More information about the Gnupg-devel