From: Martin Kletzander <mkletzan@redhat.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: libvir-list@redhat.com,
Xen-devel <xen-devel@lists.xenproject.org>,
phrdina@redhat.com
Subject: Re: [libvirt] Libvirt build broken
Date: Thu, 3 Nov 2016 15:04:02 +0100 [thread overview]
Message-ID: <20161103140402.GB7186@wheatley> (raw)
In-Reply-To: <20161103135017.GW30231@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1362 bytes --]
On Thu, Nov 03, 2016 at 01:50:17PM +0000, Wei Liu wrote:
>Hi
>
>Xen Project's CI system found a build failure between libvirt changes
>06a7b1ff..478ddedc. I don't think this is Xen specific FWIW.
>
My guess is either 680d2f49dad425395de627a31006cb84848cfa65 or
0c62ccf927c60c9c248db52a23670ec2f9bce2b2 as those are the two that touch
gnutls configure stuff.
>The build log can be found at:
>
>http://logs.test-lab.xenproject.org/osstest/logs/101868/build-amd64-libvirt/5.ts-libvirt-build.log
>
>The first error:
>
> CC libvirt_driver_la-libvirt-host.lo
>libvirt.c:320:15: error: variable 'virTLSThreadImpl' has initializer but incomplete type
> static struct gcry_thread_cbs virTLSThreadImpl = {
> ^
>Earlier in configure:
>
> configure: gnutls: no
>
>>From the look of it configure doesn't work properly anymore.
>
There are two problems here. One is that you probably have old gnutls
(older than 2.2.0, for more info check the two commits). That's why you
are not building with gnutls, but the real problem here (which is in the
code) is that we are not able to build without gnutls (my quick guess).
We are using struct gcry_thread_cbs even when building without gnutls
and that's what should be fixed, IMHO.
>
>Wei.
>
>--
>libvir-list mailing list
>libvir-list@redhat.com
>https://www.redhat.com/mailman/listinfo/libvir-list
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-03 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 13:50 Libvirt build broken Wei Liu
2016-11-03 14:03 ` [libvirt] " Olga Krishtal
2016-11-03 14:04 ` Martin Kletzander [this message]
2016-11-03 14:58 ` Pavel Hrdina
[not found] ` <20161103145804.GC7746@antique-desktop>
2016-11-03 15:03 ` Wei Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161103140402.GB7186@wheatley \
--to=mkletzan@redhat.com \
--cc=libvir-list@redhat.com \
--cc=phrdina@redhat.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).