W32 build fixes for gnupg-2.0.19

[LRN]

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

On 01.02.2013 18:54, Werner Koch wrote:
> On Fri,  1 Feb 2013 13:11, lrn1986 at gmail.com said:
> 
>> What is that way? GnuPG4Win? Or do you use *gasp* MSVC?
> 
> For a dozen years or so this is:
> 
> ./autogen.sh --build-w32
> 
OK. That is cross-compiling from a POSIX system. Using mingw
cross-compiler.

> The GnuPG built with MinGW wouldn't work well wrt PC/SC service and
> emulation of Unix domain socket.

Clarify this for me, please. How could GnuPG compiled with mingw
cross-compiler work fine (since that is the recommended way of
building it), and GnuPG compiled with mingw native compiler not work
fine? Both build methods are identical, the only difference is in
host/build values, maybe compiler flags, and the fact that you do not
run tests when cross-compiling.

Are you, by chance, confusing mingw-gcc (which produces native W32
binaries) with msys-gcc (which produces binaries linked to msys POSIX
compatibility library)? Because i'm using the former (msys here is
only used to run shell scripts - configure and such), not the latter.
No UNIX domain socket emulation is in play here.

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

iQEcBAEBAgAGBQJRC+66AAoJEOs4Jb6SI2CwRTEH/3UvloCBrm+y2eydHwU9RUzY
NcY6GIeGZh977DI8Cr75BeD1K3yPnT4ysrK6xLfGTeciejwOmaXf5lDzpGEAXSyr
832GQGI6cYWPhzTCctDI0iFzAkBScitc/dIxf+0kTp1NDGT6RryelaJJ/B/CU3kV
PSUhevCbrVMNrOq1/SQtP9csijnY3E55+1b3T+AzWt9v5W5UZtFrRrn3o9qIc3R1
KuZgZDvy8nCQ1IHgGO6StjvniVHxnQ4amMAXndagx9eFB5tyVqYHMVnif/C4Jx66
USF2eDfao13oqXPhnsHMc4eKTEe1I+BH3OTYHYjfzaDzx6JLNkX014u6fiwQIhI=
=b7zk
-----END PGP SIGNATURE-----