diff options
| author | Mark Asselstine <mark.asselstine@windriver.com> | 2018-08-17 16:43:27 -0400 |
|---|---|---|
| committer | Bruce Ashfield <bruce.ashfield@windriver.com> | 2018-08-20 11:35:48 -0400 |
| commit | cdd4241dd7a122418b3bb70b7c4e940f6dbca3b4 (patch) | |
| tree | a188fd13c68463259cc769cf63555a9b7148619d /recipes-networking/openvswitch/openvswitch-git/systemd-update-tool-paths.patch | |
| parent | 55419ec23143f35667bc895d482abc2b7e04c4e3 (diff) | |
| download | meta-virtualization-cdd4241dd7a122418b3bb70b7c4e940f6dbca3b4.tar.gz | |
libvirt: fixup ptest to prevent attempts to build tests on the target
Oddly something seems to have changed since I did the uprev of libvirt
to v4.3.0. Previously using the 'run-ptests' script would only run the
tests and not attempt to build them first. In preparation for the
uprev to v4.5.0 I attempted to run the tests and found that they would
fail to run and instead the tests were attempting to be built. I
suspect this change is caused by an uprev of autotools and the
handling of the 'TESTS' built-in.
To prevent this we are explicitly using the '--with-test-suite'
configure option and this return the previously observed behavior,
where the tests are simply run and not built.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'recipes-networking/openvswitch/openvswitch-git/systemd-update-tool-paths.patch')
0 files changed, 0 insertions, 0 deletions