On Mon, Mar 14, 2016 at 08:26:42PM +0300, Vasiliy Tolstov wrote:
> libvirt.c:323:15: error: 'gcry_thread_cbs' is deprecated
> [-Werror=deprecated-declarations]
> static struct gcry_thread_cbs virTLSThreadImpl = {
> ^
> In file included from libvirt.c:58:0:
> /usr/x86_64-pc-linux-gnu/include/gcrypt.h:211:8: note: declared here
> struct gcry_thread_cbs
> ^
> libvirt.c:331:5: error: excess elements in struct initializer [-Werror]
> virTLSMutexInit,
> ^
> libvirt.c:331:5: note: (near initialization for 'virTLSThreadImpl')
> libvirt.c:332:5: error: excess elements in struct initializer [-Werror]
> virTLSMutexDestroy,
> ^
> libvirt.c:332:5: note: (near initialization for 'virTLSThreadImpl')
> libvirt.c:333:5: error: excess elements in struct initializer [-Werror]
> virTLSMutexLock,
> ^
> libvirt.c:333:5: note: (near initialization for 'virTLSThreadImpl')
> libvirt.c:334:5: error: excess elements in struct initializer [-Werror]
> virTLSMutexUnlock,
> ^
> libvirt.c:334:5: note: (near initialization for 'virTLSThreadImpl')
This is caused by changes in latest version of libgcrypt.
Most people don't hit this because when building with latest gnutls,
libvirt will prefer linking to nettle, instead of libgcrypt. ie linking
to modern gnutls and modern libgcrypt is pretty unusual setup. Are you
perhaps missing nettle-devel packages causing it to fallback to the
legacy libgcrypt codepath ?
None the less we should fix libvirt to not have these libgcrypt errors.
Regards,
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 :|
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list