xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Pavel Hrdina <phrdina@redhat.com>
Cc: libvir-list@redhat.com,
	Xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: Libvirt build broken
Date: Thu, 3 Nov 2016 15:03:42 +0000	[thread overview]
Message-ID: <20161103150342.GA9685@citrix.com> (raw)
In-Reply-To: <20161103145804.GC7746@antique-desktop>

On Thu, Nov 03, 2016 at 03:58:04PM +0100, Pavel Hrdina wrote:
> 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.
> > 
> > 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 
> 
> Hi
> 
> I've just pushed a patch that fixes this build issue:
> 
> <https://www.redhat.com/archives/libvir-list/2016-November/msg00206.html>
> 

Thanks!

Wei.

> Pavel



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      parent reply	other threads:[~2016-11-03 15:06 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
2016-11-03 14:58 ` Pavel Hrdina
     [not found] ` <20161103145804.GC7746@antique-desktop>
2016-11-03 15:03   ` Wei Liu [this message]

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=20161103150342.GA9685@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=libvir-list@redhat.com \
    --cc=phrdina@redhat.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).