From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Razvan Cojocaru' <rcojocaru@bitdefender.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen staging: libxendevicemodel.so.1 [...] not found
Date: Thu, 2 Mar 2017 09:28:40 +0000 [thread overview]
Message-ID: <17b3db3ad3bb4d1bb2f99e0552cea348@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <83063579-4827-e86b-daa3-7fb417675e2e@bitdefender.com>
> -----Original Message-----
> From: Razvan Cojocaru [mailto:rcojocaru@bitdefender.com]
> Sent: 02 March 2017 09:27
> To: Paul Durrant <Paul.Durrant@citrix.com>; Xen-devel <xen-
> devel@lists.xen.org>
> Subject: Re: [Xen-devel] Xen staging: libxendevicemodel.so.1 [...] not found
>
> On 03/02/2017 11:23 AM, Paul Durrant wrote:
> >> -----Original Message-----
> >> From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of
> >> Razvan Cojocaru
> >> Sent: 02 March 2017 09:19
> >> To: Xen-devel <xen-devel@lists.xen.org>
> >> Subject: [Xen-devel] Xen staging: libxendevicemodel.so.1 [...] not found
> >>
> >> Hello,
> >>
> >> Just pulled the latest staging and I get:
> >>
> >> qemu successfuly configured for Xen qemu-dm build
> >> === PCI passthrough capability has been enabled ===
> >> make[2]: Entering directory
> >> `~/work/xen.git/tools/qemu-xen-traditional-dir-remote'
> >> === PCI passthrough capability has been enabled ===
> >> === PCI passthrough capability has been enabled ===
> >> make[3]: Entering directory
> >> `~/work/xen.git/tools/qemu-xen-traditional-dir-remote/i386-dm'
> >> LINK i386-dm/qemu-dm
> >> /usr/bin/ld: warning: libxendevicemodel.so.1, needed by
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so, not found (try using
> >> -rpath or -rpath-link)
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_map_pcidev_to_ioreq_server@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_get_ioreq_server_info@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_open@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_unmap_io_range_from_ioreq_server@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_modified_memory@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_set_ioreq_server_state@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_track_dirty_vram@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_close@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_set_mem_type@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_destroy_ioreq_server@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_set_pci_intx_level@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_create_ioreq_server@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_unmap_pcidev_from_ioreq_server@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_inject_event@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_set_pci_link_route@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_inject_msi@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_set_isa_irq_level@VERS_1.0'
> >> ~/work/xen.git/tools/../tools/libxc/libxenctrl.so: undefined reference
> >> to `xendevicemodel_map_io_range_to_ioreq_server@VERS_1.0'
> >> collect2: error: ld returned 1 exit status
> >> make[3]: *** [qemu-dm] Error 1
> >>
> >> Just thought somebody'd like to know.
> >>
> >
> > Are you using a custom qemu-trad? You need to make sure it has the
> following patches applied:
> >
> > http://xenbits.xen.org/gitweb/?p=qemu-xen-
> traditional.git;a=commit;h=58b9047bf2da88d2976bd1b7ba50dfdcc68b503d
> > http://xenbits.xen.org/gitweb/?p=qemu-xen-
> traditional.git;a=commit;h=8b4834ee1202852ed83a9fc61268c65fb6961ea7
>
> No, just did ./configure --disable-systemd --prefix=/usr and a make
> dist. Those patches have not made it into staging yet apparently - git
> log doesn't show them. I'll apply them manually.
The tag in staging has been updated. If you do a 'make mrproper' or just blow away your qemu-trad repo then 'make tools' should updated it for you.
Paul
>
>
> Thanks,
> Razvan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-02 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 9:19 Xen staging: libxendevicemodel.so.1 [...] not found Razvan Cojocaru
2017-03-02 9:23 ` Paul Durrant
2017-03-02 9:27 ` Razvan Cojocaru
2017-03-02 9:28 ` Paul Durrant [this message]
2017-03-02 9:43 ` 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=17b3db3ad3bb4d1bb2f99e0552cea348@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=rcojocaru@bitdefender.com \
--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).