W32 build fixes for gnupg-2.0.19

[LRN]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01.02.2013 14:16, NIIBE Yutaka wrote:
> Hello,
> 
> Thanks for your effort and explanation.
> 
> On 2013-02-01 at 07:11 +0400, LRN wrote:
>> On 26.01.2013 23:37, Werner Koch wrote:
>>> On Sat, 26 Jan 2013 04:47, lrn1986 at gmail.com said:
>>>> Subj is attached.
>>> 
>>> Please explain the problems you are trying to fix.
>> The single problem is GnuPG not building with MinGW/MSys.
> 
> Well, then, my question is:
> 
> Why on earth do you need to build GnuPG with MinGW/Msys
Because i build everything with MinGW/MSys. I can build gcc, binutils,
pthreads, and over 100 other packages.
GnuPG can not be (should not be) special in this regard.

> , given we have another recommended way to build GnuPG for
> Windows?
What is that way? GnuPG4Win? Or do you use *gasp* MSVC?

> 
> I'm afraid that it would result another incompatible GnuPG.
That will not be a problem. Or, rather, it will not be a problem for
_you_.

> My major concern is using smartcard/token and/or gpg-agent.  The
> GnuPG built with MinGW wouldn't work well wrt PC/SC service and
> emulation of Unix domain socket.
Why?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRC7DXAAoJEOs4Jb6SI2CwYB8IAMkhKNyzbsUkZqaxunBxI2EA
DGHHZo7Lg2QhK9CMjkdFnnoOvLURl350Etotkotu2ukv1hPmqKke2FhY8cd8Kw+V
JF/q0WCseoRvqV6wYyiHUqedr6YYZhEPswt5XrWptgkg+aNfUHmEMdp/CZZx9AoC
hg/HZrH+XbEHg/DoSYvq9v8C3hbi/ZhO+Gbh02QEfmpvyJi523VO8a0398qz+Dyk
+qVbgRhEzqXBdgpx3zAbFqW1+ZnqVmxxI0JPX0ZqCLUXABTKrbi/UZOJpRoyrlep
MqbP6MbwuSWhxDwQH6W2+JFUp7B6QbRBObJVJQAom399SiWrS3WbHgNWmPRnRE8=
=4E9u
-----END PGP SIGNATURE-----