Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | openvswitch: uprev to the recently released v2.7.0 | Mark Asselstine | 2017-03-29 | 1 | -7/+106 |
| | | | | | | | | | | | | | | | This version of OVS was released on Feb. 21. Bringing our recipe up to date with the latest release ensure we have all the latest CVE fixes as well as any new functionality that folks might be looking for. Additionally we are better situated to support up to date releases of DPDK (v16.11 in this case). No surprises with the uprev, it passes all usecase tests (meta-overc) and ptest results are much the same as the results we had in v2.6.1. While completing the uprev I took the opportunity to do some cleanup of patches that were no longer used or required. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> | ||||
* | openvswitch: fix build host contamination | Mark Asselstine | 2017-01-14 | 1 | -0/+53 |
There is only a single PYTHON variable for configure and yet python is used for the build as well as scripts installed on the target. If we set a path in PYTHON as we had we end up using this same path during the build and since it isn't to the sysroot we end up with host contamination (as demonstrated by python failing to import 'six' on build hosts without python-six installed. The best approach is to set PYTHON to "python" when calling configure, ie. without a path. This will use 'python' from the path during build time and by ensuring all the installed scripts use '/usr/bin/env' we can ensure python will be found on the target when the scripts are run. Since 'six' is used as part of the build we have to ensure it is -native'ly buildable and we set all the required build and runtime dependencies. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> |