http://bugs.winehq.org/show_bug.cgi?id=27036
--- Comment #15 from Henri Verbeet hverbeet@gmail.com 2012-03-18 17:38:00 CDT --- I don't think current versions of gnutls use libgcrypt anymore, so at least as far as secur32 is concerned this should go away on its own. If it did though, I'd argue that it should be up to gnutls to properly initialize libgcrypt, e.g. in gnutls_global_init(). Wine shouldn't have to care about what crypto backend gnutls was compiled with.