On Thu, Feb 07, 2013 at 08:34:18AM -0500, Dan Winship wrote:
On 02/07/2013 07:27 AM, Daniel P. Berrange wrote:
> The other potential impact is that gnutls no longer uses libgcrypt,
> but instead uses nettle.
>
> This can impact apps that were using gnutls in a threaded environment
> because they probably have used 'gcry_control' to register a thread
> impl for gcrypt, to ensure that gnutls was thread safe.
>
> So merely rebuilding applications may well not work & require some
> code changes. This will certainly impact libvirt builds.
You can just remove the gcry_control() calls; they've been unnecessary
since gnutls 2.11.0.
Unfortunately not - libvirt code has to support versions earlier than
that - we don't mandate use of newest gnutls. We target any releae
since RHEL5 vintage or later, which means gnutls >= 1.4.x
Daniel
--
|:
http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|:
http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|