[meta-virtualization] [PATCH 0/2] libvirt: uprev and PACKAGECONFIG fixups
Bruce Ashfield
bruce.ashfield at windriver.com
Sat Aug 10 21:16:56 PDT 2013
These patches update libvirt to the July 1.1.1 release, as well as fix
some build issues I found along the way.
As for the release update, standard libvirt/libvirtd tests were run,
and the ability to launch, query and control a guest were confirmed.
Along with the 1.1.1 update, I've included a patch that fixes the
virNetTLSInit unresolved symbol error that has been reported several
times in the past. As the patch states, this fix isn't perfect, since
there must be some libtool magic that could be used to make the
link change I'm showing be automatically applied .. but I couldn't make
it work, and instead have a blunter approach. If anyone wants to tackle
a better fix, patches are welcome.
I'm keeping 1.0.3 around for a short while, just to ensure that 1.1.1
is fully functional.
As it turns out the virNetTLSInit link error is triggered by a bad
combination of PACKAGECONFIG values (where everything but python is
disabled for libvirt). It just so happens that this is the default
since the libvirt-python.inc file sets PACKAGECONFIG, which inhibits
the defaults you see in the libvirt recipe from ever triggering.
Everyone must be building with their own options, in their own layers
if this is working for people.
By pulling the python PACKAGECONFIG back into the main recipe and
ensuring that PACKAGECONFIG_${PN} is used in the python.inc, we get
the default options building again.
I've confirmed that things build here, but YMMV and error reports
and patches are welcomed.
If no one objects, I'll push these patches on Monday.
Cheers,
Bruce
More information about the meta-virtualization
mailing list