qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Paul Durrant <Paul.Durrant@citrix.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Wei Liu <wei.liu2@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Qemu-devel] QEMU build breakage on ARM against Xen 4.9 caused by libxendevicemodel
Date: Wed, 3 May 2017 18:51:40 +0100	[thread overview]
Message-ID: <20170503175140.GD1553@perard.uk.xensource.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1705031019140.9240@sstabellini-ThinkPad-X260>

On Wed, May 03, 2017 at 10:20:59AM -0700, Stefano Stabellini wrote:
> On Wed, 3 May 2017, Anthony PERARD wrote:
> > On Thu, Apr 20, 2017 at 11:05:33AM -0700, Stefano Stabellini wrote:
> > > On Thu, 20 Apr 2017, Paul Durrant wrote:
> > > > I think xencall should be part of the base xen_stable_libs anyway.
> > > 
> > > Yes, you are right. However I noticed that -lxencall needs to come after
> > > -lxendevicemodel. So, I'll have to move -lxendevicemodel before
> > > $xen_stable_libs, see below. I'll merge this patch into "configure:
> > > detect presence of libxendevicemodel", if that's OK.
> > > 
> > > diff --git a/configure b/configure
> > > index 99d6cbc..3133ef8 100755
> > > --- a/configure
> > > +++ b/configure
> > > @@ -1992,7 +1992,7 @@ if test "$xen" != "no" ; then
> > >    else
> > >  
> > >      xen_libs="-lxenstore -lxenctrl -lxenguest"
> > > -    xen_stable_libs="-lxenforeignmemory -lxengnttab -lxenevtchn"
> > > +    xen_stable_libs="-lxencall -lxenforeignmemory -lxengnttab -lxenevtchn"
> > >  
> > >      # First we test whether Xen headers and libraries are available.
> > >      # If no, we are done and there is no Xen support.
> > > @@ -2027,9 +2027,9 @@ int main(void) {
> > >    return 0;
> > >  }
> > >  EOF
> > > -        compile_prog "" "$xen_libs $xen_stable_libs -lxendevicemodel"
> > > +        compile_prog "" "$xen_libs -lxendevicemodel $xen_stable_libs"
> > >        then
> > > -      xen_stable_libs="$xen_stable_libs -lxendevicemodel"
> > > +      xen_stable_libs="-lxendevicemodel $xen_stable_libs"
> > >        xen_ctrl_version=40900
> > >        xen=yes
> > >      elif
> > 
> > Hey, now that this patch is merged, xen.git fail to build QEMU. (osstest
> > qemu-mainline branch fail.)
> > 
> > That's because -lxencall is not found because -L$path_to_libxencall is
> > missing in xen.git.
> > 
> > But I've notice something else, libxendevicemodel.so is not linked
> > against libxencall, that might be the root of the issues on arm.
> > (libxenctrl.so is linked against libxencall.)
> > 
> > Thought?
> > 
> > 
> > We probably need this patch in xen:
> 
> We also need to add -L$path_to_libxencall and -I$path_to_libxencall to
> tools/Makefile:subdir-all-qemu-xen-dir.

I don't think that needed because:
for -I, QEMU does not use anything from xencall, and any other includes
does not use xencall.h.

for -L, I think that would be usefull only if QEMU is built staticly.

Also, I don't think -lxencall is needed at all, if libxendevicemodel is
fixed. libxencall will only be a runtime dependency.


> > diff --git a/tools/libs/devicemodel/Makefile b/tools/libs/devicemodel/Makefile
> > index 55626a5049..81fa5a4ac4 100644
> > --- a/tools/libs/devicemodel/Makefile
> > +++ b/tools/libs/devicemodel/Makefile
> > @@ -63,7 +63,7 @@ libxendevicemodel.so.$(MAJOR): libxendevicemodel.so.$(MAJOR).$(MINOR)
> >         $(SYMLINK_SHLIB) $< $@
> >  
> >  libxendevicemodel.so.$(MAJOR).$(MINOR): $(PIC_OBJS) libxendevicemodel.map
> > -       $(CC) $(LDFLAGS) $(PTHREAD_LDFLAGS) -Wl,$(SONAME_LDFLAG) -Wl,libxendevicemodel.so.$(MAJOR) $(SHLIB_LDFLAGS) -o $@ $(PIC_OBJS) $(LDLIBS_libxentoollog) $(APPEND_LDFLAGS)
> > +       $(CC) $(LDFLAGS) $(PTHREAD_LDFLAGS) -Wl,$(SONAME_LDFLAG) -Wl,libxendevicemodel.so.$(MAJOR) $(SHLIB_LDFLAGS) -o $@ $(PIC_OBJS) $(LDLIBS_libxentoollog) $(LDLIBS_libxencall) $(APPEND_LDFLAGS)
> >  
> >  .PHONY: install
> >  install: build
> > 
> > -- 
> > Anthony PERARD
> > 

-- 
Anthony PERARD

  reply	other threads:[~2017-05-03 17:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14 22:50 [Qemu-devel] QEMU build breakage on ARM against Xen 4.9 caused by libxendevicemodel Stefano Stabellini
2017-04-15  0:39 ` Stefano Stabellini
2017-04-18 10:00   ` Paul Durrant
2017-04-18 17:40     ` Stefano Stabellini
2017-04-19  8:43       ` Paul Durrant
2017-04-19 23:02         ` Stefano Stabellini
2017-04-20  8:02           ` Paul Durrant
2017-04-20 18:05             ` Stefano Stabellini
2017-04-21  8:29               ` Paul Durrant
2017-05-03 16:48               ` Anthony PERARD
2017-05-03 16:52                 ` Wei Liu
2017-05-03 16:55                   ` Anthony PERARD
2017-05-04 11:08                     ` Wei Liu
2017-05-03 16:52                 ` Paul Durrant
2017-05-03 17:20                 ` Stefano Stabellini
2017-05-03 17:51                   ` Anthony PERARD [this message]
2017-05-03 20:30                     ` Stefano Stabellini
2017-05-03 20:38                       ` Stefano Stabellini

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=20170503175140.GD1553@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.org \
    --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).