mirror of
https://git.yoctoproject.org/poky
synced 2026-09-14 12:49:34 +02:00
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] (From OE-Core rev: 5b413d1fdb4bdbaec86d630bb52c3ccf68aae789) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
364880dcb3
commit
1c5a2c8bcc
@@ -234,6 +234,5 @@ PREMIRRORS = "\\
|
||||
|
||||
class Poisoning(OESelftestTestCase):
|
||||
def test_poisoning(self):
|
||||
res = bitbake("poison", ignore_status=True)
|
||||
self.assertNotEqual(res.status, 0)
|
||||
self.assertTrue("is unsafe for cross-compilation" in res.output)
|
||||
# The poison recipe fails if the poisoning didn't work
|
||||
bitbake("poison")
|
||||
|
||||
Reference in New Issue
Block a user