xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: libvir-list@redhat.com
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	Jim Fehlig <jfehlig@suse.com>, Wei Liu <wei.liu2@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Fixing libvirt's libxl driver breakage -- where to define LIBXL_API_VERSION?
Date: Tue, 5 Apr 2016 12:39:36 +0100	[thread overview]
Message-ID: <20160405113936.GA18120__28777.6395598941$1459856417$gmane$org@citrix.com> (raw)

Hi libvirt maintainers,

Xen's control library libxenlight (libxl) requires application
(libvirt in this case) to explictily define LIBXL_API_VERSION. This is
lacking at the moment so libvirt's libxl driver always gets the latest
APIs. We changed one of the APIs in libxl so libvirt's libxl driver
can't build at the moment.

I want to submit a patch for libvirt to define LIBXL_API_VERSION, but
I'm not sure where I should add that to. Can you give me some
pointers? Or even better -- a specific file that I should edit?
src/Makefile.am and src/Makfile.in are good candicate to me as far as
I can tell.

Thanks
Wei.

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

             reply	other threads:[~2016-04-05 11:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 11:39 Wei Liu [this message]
     [not found] <20160405113936.GA18120@citrix.com>
2016-04-12 21:31 ` Fixing libvirt's libxl driver breakage -- where to define LIBXL_API_VERSION? Jim Fehlig
     [not found] ` <570D6942.8020106@suse.com>
2016-04-12 22:06   ` Wei Liu
2016-04-13  9:09   ` George Dunlap
2016-04-13 23:31     ` Jim Fehlig
     [not found]     ` <570ED6B4.3060102@suse.com>
2016-04-14  7:40       ` Dario Faggioli
     [not found]       ` <1460619652.13871.130.camel@citrix.com>
2016-04-14 17:59         ` Ian Jackson
2016-04-14 18:05           ` Dario Faggioli
2016-04-15  9:14           ` Olaf Hering

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='20160405113936.GA18120__28777.6395598941$1459856417$gmane$org@citrix.com' \
    --to=wei.liu2@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=jfehlig@suse.com \
    --cc=libvir-list@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).