[OE-core] [PATCH 0/7] linux-yocto: consolidated pull request

Bruce Ashfield bruce.ashfield at gmail.com
Wed Mar 28 12:57:09 UTC 2018


On Wed, Mar 28, 2018 at 8:07 AM, Burton, Ross <ross.burton at intel.com> wrote:
> On 28 March 2018 at 13:01, Bruce Ashfield <bruce.ashfield at gmail.com> wrote:
>> On Wed, Mar 28, 2018 at 6:33 AM, Burton, Ross <ross.burton at intel.com> wrote:
>>> Also a non-musl target failed like this:
>>>
>>> | NOTE: FAIL [6.426s]: test_kernel_module (kernelmodule.KernelModuleTest)
>>> | NOTE: ----------------------------------------------------------------------
>>> | NOTE: Traceback (most recent call last):
>>> |   File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/meta/lib/oeqa/core/decorator/__init__.py",
>>> line 32, in wrapped_f
>>> |     return func(*args, **kwargs)
>>> |   File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/meta/lib/oeqa/core/decorator/__init__.py",
>>> line 32, in wrapped_f
>>> |     return func(*args, **kwargs)
>>> |   File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/meta/lib/oeqa/core/decorator/__init__.py",
>>> line 32, in wrapped_f
>>> |     return func(*args, **kwargs)
>>> |   File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/meta/lib/oeqa/runtime/cases/kernelmodule.py",
>>> line 40, in test_kernel_module
>>> |     self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
>>> | AssertionError: 2 != 0 : cd /tmp && make
>>> | make -C /usr/src/kernel M=/tmp modules
>>> | make[1]: Entering directory '/usr/src/kernel'
>>> | make[2]: *** No rule to make target 'tools/objtool/objtool', needed
>>> by '/tmp/hellomod.o'.  Stop.
>>> | make[1]: Leaving directory '/usr/src/kernel'
>>> | make[1]: *** [Makefile:1519: _module_/tmp] Error 2
>>> | make: *** [Makefile:5: all] Error 2
>>>
>>> Same error but with glibc instead of musl.
>>
>> That's the annoying new dependency kicking in, it keeps sneaking back
>> with -stable updates
>> and it is maddening.
>>
>> What kernel version is this 4.14 ? If so, I'll need to add the
>> dependency lines from the 4.15
>> to 4.14 as well .. after just doing that for 4.12.
>
> Yes, 4.13.30 on x86-64 only, interestingly.  Not sure if that's the
> test matrix being odd, or the kernel.

Nope. That's what I expected, for the 4.14+ kernels, I had to add:

DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"

And it has now come back to the -stable kernel to haunt me.

I'll send another patch to add the dependency, and we should be good. If it
doesn't fix the problem, then 4.15 should be blowing up in the same way.

Bruce

>
> Ross



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"



More information about the Openembedded-core mailing list