]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commit
oeqa/poisoning: fix gcc include poisoning test
authorRoss Burton <ross.burton@arm.com>
Tue, 21 Jan 2025 18:23:08 +0000 (18:23 +0000)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 22 Jan 2025 13:20:20 +0000 (13:20 +0000)
commit5b413d1fdb4bdbaec86d630bb52c3ccf68aae789
tree050603ada887d667edaa6cc8f4c40d70bc639358
parent6cf0aaa3af276694709369b6007f629862e21559
oeqa/poisoning: fix gcc include poisoning test

The test code in poison was flawed: as long as one CPP/CC/CXX has fatal
poisoning enabled then the test passes.  However, at the moment due to
a bad rebase only CPP has fatal poisoning and CC/CXX do not.

Rewrite the do_compile() task to more carefully check the output so the
test harness itself just has to bitbake the recipe.

Note that this results in the test failing:

  ERROR: poison-1.0-r0 do_compile: C Compiler is not poisoned.
  Exit status 0, output:  cc1: warning: include location "/usr/include" is unsafe for cross-compilation [-Wpoison-system-directories]
  ERROR: poison-1.0-r0 do_compile: C++ Compiler is not poisoned.
  Exit status 0, output:  cc1plus: warning: include location "/usr/include" is unsafe for cross-compilation [-Wpoison-system-directories]

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta-selftest/recipes-test/poison/poison.bb
meta/lib/oeqa/selftest/cases/buildoptions.py