summaryrefslogtreecommitdiffstats
path: root/scripts/lib/resulttool/regression.py
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@gmail.com>2023-03-09 23:12:37 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2023-03-11 00:08:41 +0000
commit64c96cbe52754e803a905513d582e2d35e837cdf (patch)
treebc6f49cfde72a3111a2310cd85a0bbf004d65ab0 /scripts/lib/resulttool/regression.py
parent7c023a2f7c1398c662cf27cfe708619b2e352087 (diff)
downloadpoky-64c96cbe52754e803a905513d582e2d35e837cdf.tar.gz
perf: fix buildpaths QA warning
In the 6.2+ kernel, arm64 perf has a buildpaths QA warning as a syscall table is now being dynamically generated. That generated table includes unistd.h by absolute path, which in turn triggers the buildpaths QA warning. This could easily be patched in linux-yocto, but that would leave the QA issue in perf built from other kernel trees. So we instead to the following: - Add the perf tools directory to the include path - Modify the Makefile to have a relative path to unistd.h and pass both the relative and absolute path to the generation script - Modify the generation script to take the relative location of unistd.h as a new parameter, and use that in the generated sycalls.c file At build, the added include path of the perf source allows the relative path file to be included, and no buildpaths warning is generated. (From OE-Core rev: c8845ab59cd7c28874473618f134a5d45906d6ea) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib/resulttool/regression.py')
0 files changed, 0 insertions, 0 deletions