[Pkg-xen-devel] xen-4.2, libxl and libvirt
Ian Campbell
ijc at hellion.org.uk
Wed Apr 10 11:09:41 UTC 2013
On Thu, 2013-03-21 at 18:10 +0000, David Scott wrote:
> -- it can't find -lxenlight because it's in /usr/lib/xen-4.2/lib and
> this isn't listed as a system library directory. I notice that
> libxenctrl.so is in /usr/lib.
This use of /usr/lib/xen-X.Y is too allow parallel installation of the
Xen tools in the case of the "internal" libraries (libxenctrl and
libxenguest etc) which are not well managed wrt SONAMES upstream.
However libxenlight isn't an internal library and it is intended to be
consumed by 3rd parties and we want to do a good job of SONAME
maintenance (and would appreciate bug reports where we fail) so I think
there is no reason no to put it in /usr/lib/{triplet}, possibly/probably
in a properly named libxenlight$SONAME package too.
> I experimented by adding '--with-libxl=/usr/lib/xen-4.2/lib' to the
> configure step, which gets me slightly further:
May need additional hacks like -L/usr/lib/... on LDFLAGS?
> I don't know whether you would consider this a problem with the xen
> package or the libvirt package. If libvirt, do you know how the libvirt
> package should be modified? Is the plan to have multiple libxenlights
> installed (/usr/lib/xen-4.3/lib)? If so, how would a libvirt package
> choose one to link to?
Probably the one which libxenlight-dev includes, whichever that is?
Multiple backends is a theoretical possibility but would likely involve
lots of hoops and jumping through them for all parties concerned...
>
> Any help or advice greatly appreciated! :-)
>
> Thanks,
> Dave
>
> _______________________________________________
> Pkg-xen-devel mailing list
> Pkg-xen-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xen-devel
>
More information about the Pkg-xen-devel
mailing list