RFC: deploying libmingwex-0.dll

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

Guys,

The issue arose as an unintentionally introduced dependency, when I 
published GCC-6.3.0; I rebuilt the gcc-core-bin component, to correct 
an mpc-1.0.2 header vs. mpc-1.0.3 library dependency inconsistency, 
after I'd added libmingwex.dll.a to my cross-compiler tools.

Unintentional, it may have been, but entirely undesirable?  I'm not 
sure.  Now that this dynamic linking option is available, would it not 
be a worthwhile deployment choice to have *all* MinGW.org tools linked 
thus?  (After all, dynamic linking does have its advantages, in spite 
of the aversion shown by many Windows users).

What do you think?

- -- 
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJZdzHdAAoJEMCtNsY0flo/jvMQAKfIfniiSQKC0c4Xy6h7OCuC
hpwUolJ2DAbw3Dd5fOWgRfahcC6OTYtrXqk1UpwVbz/iFTSc+SmULUdSg8xSz9pR
9nSyt/RlM537AEvpgcKgbDDHWOsG5mvbIp9W1lIQbhIIr/JqK4iiLnzWmc84ClGz
wSb8otcdBtsrCZi3hxi/JmvoUy1yRN3m5XuaIEtOoSkQqfV3GvZyva2o63GhjuL5
+ygEwB1B05ONDK3vt78n4L4T61JD0bXBHnPhov30K4OM/43YkHCWqhhM7FMTnsRh
mBXi1BhEaGw+L4TlvRNg7eTpbM3fRRiD7WeNXj2rj9OPv2m3piqgCtT/fs1a99fl
Hpch8mLLwakhUqaKZ3UNZoFlbrV3m2L6McVhQgYjH+hFwp8I7kE16sVzkAHoaj4P
ubTHOLdDj6Mc4+760p4TbDE7ECGoNeNzoowLn5k+hEVNL5aqFfKmuiH5NQIkJUxz
ExQNxMMkWTzwwRKkTbMCMFRp8m8eL5dL/KZuDdgqO/Xb3ecDJdllAJtOpVzt6qC4
k+lVMV+Pg/nvYluLdwGIDHGMFhINjS4BQFkEqLadW90z/C8YPBIoCUndvFbFNud6
jTNaMIuh5ZjzX61scKDRpntu8kUgYeVC/TgSoarXHbrEgsJxqQqAVQG+ZsuIg17h
KCSxNvtzrXP7pFM9oF3g
=oCqf
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot