xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Anthony PERARD <anthony.perard@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Cc: Wei Liu <Wei.Liu2@citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	et@etit.hu, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	George Dunlap <dunlapg@umich.edu>
Subject: Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04
Date: Fri, 10 Jun 2016 09:30:03 -0600	[thread overview]
Message-ID: <575AF91B02000078000F40B4@prv-mh.provo.novell.com> (raw)
In-Reply-To: <575AF7CF02000078000F40A0@prv-mh.provo.novell.com>

>>> On 10.06.16 at 17:24, <JBeulich@suse.com> wrote:
>>>> On 10.06.16 at 17:00, <sstabellini@kernel.org> wrote:
>> On Fri, 10 Jun 2016, Anthony PERARD wrote:
>>> On Fri, Jun 10, 2016 at 01:14:43PM +0100, Ian Jackson wrote:
>>> > George Dunlap writes ("Re: [Xen-devel] compilation fail, xen staging-4.6, 
>> vnc.c, qemu-tradintional issues under ubuntu 16.04"):
>>> > > Anthony / Stefano / Ian, this is still failing two months later:
>>> > > 
>>> > > vl.c: In function ‘main’:
>>> > > vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
>>> > > [-Werror=deprecated-declarations]
>>> > >      g_mem_set_vtable(&mem_trace);
>>> > >      ^
>>> > > In file included from /usr/include/glib-2.0/glib/glist.h:32:0,
>>> > >                  from /usr/include/glib-2.0/glib/ghash.h:33,
>>> > >                  from /usr/include/glib-2.0/glib.h:50,
>>> > >                  from vl.c:59:
>>> > > /usr/include/glib-2.0/glib/gmem.h:357:6: note: declared here
>>> > >  void  g_mem_set_vtable (GMemVTable *vtable);
>>> > >       ^
>>> > > cc1: all warnings being treated as errors
>>> > > /root/git/xen.git/tools/qemu-xen-dir/rules.mak:57: recipe for target
>>> > > 'vl.o' failed
>>> > 
>>> > Anthony, perhaps while you're looking at the XSA-180 backports you
>>> > could look at this too ?
>>> > 
>>> > (I can confirm that with qemu-xen staging-4.6, git-grep
>>> > g_mem_set_vtable produces some output, but I haven't investigated
>>> > further.  I don't know which Xen branches are affected.)
>>> > 
>>> > I think this should be fixed for the forthcoming 4.6 point release,
>>> > ideally.
>>> 
>>> I've push upstream commit 98cf48f (trace: remove malloc tracing) to
>>> qemu-xen staging-4.6 and 4.5.
>> 
>> In that case we'll need new tags. 4.6.3? 4.6.2.1?
> 
> 4.6.2a or 4.6.2b I would say, as the main release number is still
> going to be 4.6.2.

But wait - the subject says qemu-trad, which didn't get tagged yet.
Did these commits go into the qemu-xen tree really? I guess I'm
confused now...

Jan

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

  reply	other threads:[~2016-06-10 15:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOz6fc-Bx2q_waP38T4c==TLiGwOSfKeU0XHOdv-XEGrdvWW-w@mail.gmail.com>
     [not found] ` <alpine.OSX.2.20.1603231218290.753@mac>
2016-03-25 17:53   ` compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04 Éliás Tamás
2016-03-30 14:58     ` Dario Faggioli
2016-03-31 22:08       ` [Xen-users] " Éliás Tamás
2016-06-10 11:26       ` George Dunlap
2016-06-10 12:14         ` Ian Jackson
2016-06-10 14:55           ` Anthony PERARD
2016-06-10 15:00             ` Stefano Stabellini
2016-06-10 15:24               ` Jan Beulich
2016-06-10 15:30                 ` Jan Beulich [this message]
2016-06-10 15:38                   ` George Dunlap
2016-06-13 13:36                     ` Ian Jackson
2016-06-10 14:00         ` Anthony PERARD
2016-06-10 14:08           ` George Dunlap
2016-06-10 14:22             ` Anthony PERARD

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=575AF91B02000078000F40B4@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Wei.Liu2@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=dunlapg@umich.edu \
    --cc=et@etit.hu \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.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).