| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
1.1.2 is available and fixes a number of issues with 1.1.1 (segfaults
and more).
Since 1.1.1 has been available for a while, with no significant issues
reported, I'm also removing the fallback 1.0.3 and 1.1.1 recipes with
this update.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
| |
During the 1.1.1 uprev, a debug change of overly aggressive packaging
was left in place. The restores the previous packaging divisions.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The libvirt-python.inc manipulation of PACKAGECONFIG meant that the default
configuration options of the libvirt recipe never fired, since the variable
had an assignment and the lazy set of the configuration values never
applied to the build.
Moving the python PACKAGE_CONFIG options into the main recipe, and ensuring
that PACKAGE_CONFIG_${PN} is used for libvirt-python means that most builds
will now use the default configuration.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
|
Updating to the 1.1.1 libvirt release. Changes from the 1.0.3 recipe include
a fix/workaround for the:
../src/.libs/libvirt.so: undefined reference to `virNetTLSInit'
That is seen on some machines. The current fix is to explicilty link against
the library which provides the definition. A smarter fix via libtool may
be possible, but was elusive at the time of writing this patch.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
