summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/automake/automake/new_rt_path_for_test-driver.patch
Commit message (Collapse)AuthorAgeFilesLines
* automake: 1.15.1 -> 1.16.1Robert Yang2018-07-051-5/+17
| | | | | | | | | | | | | | | * Refreshed the following patches: - 0001-automake-Add-default-libtool_tag-to-cppasm.patch - automake-replace-w-option-in-shebangs-with-modern-use-warnings.patch - buildtest.patch - new_rt_path_for_test-driver.patch - performance.patch - python-libdir.patch (From OE-Core rev: f63a493298de7d0cac36a65dafba5dae06c06a05) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* automake: set test-driver path relative to top_builddirMartin Borg2016-02-281-0/+36
automake offers auxiliary tools and is capable to install and prepare the setup for those. test-driver, a log driver used by parallel testsuite harness in ptests, is one of those tools. By default it looks that automake prepare environment for testing relative $top_srcdir. But in Yocto following changed: - build folder was separated - $top_srcdir is not anymore defined as relative path, now can be relative or absolute So now in Yocto the Makefile from src/tests contains absolute path of $top_srcdir for test-driver which is an unexisting path at runtime. We need to have relative path for test-driver in Makefile to work on target. $top_builddir can guarantee this path. Originally submitted by Adrian Calianu <adrian.calianu@enea.com> (From OE-Core rev: e9db0ae11d95f3c375b27d5c10606efd8b568fbf) Signed-off-by: Martin Borg <martin.borg@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>