Bug 11421

Summary: Crops-ESDK: devtool build v4l2loopback-driver, fails when trying to access /lib/modules/<laptop_kernel_version>
Product: [Yocto Project Subprojects] CROPS Reporter: Libertad <libertad.gonzalez.de.la.cruz>
Component: crops-defaultAssignee: Todor Minchev <todor.minchev>
Status: RESOLVED FIXED QA Contact: Libertad <libertad.gonzalez.de.la.cruz>
Severity: normal    
Priority: Medium CC: bluelightning, brian.avery, patrick.ohly
Version: 2.3   
Target Milestone: 2.3 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
shows failed build action none

Description Libertad 2017-04-26 19:55:02 UTC 
Created attachment 3756 [details]
shows failed build action

DESCRIPTION:

Within the crops container when trying to build v4l2loopback-driver it gives out an error that says oe_runmake failed and that function do_install failed.

STATUS: FAILED
BUILD: 2.3 M4: rc2-7a0e795373653886452a7a2992ced10080711c26
ENVIRONMENT: user-preference (any supported environment)

STEPS TO REPRODUCE: 
Step 1. Initiate your Crops-esdk environment 

docker run --rm -it -v /home/libby/sdkstuff:/workdir crops/extsdk-container --url http://localhost/poky-glibc-x86_64-core-image-sato-i586-toolchain-2.3.sh

Step 2: source environment-setup-i586-poky-linux

Step 3: run command which devtool

Step 4: devtool add v4l2loopback-driver  https://github.com/umlaeute/v4l2loopback.git

Step 5: devtool build v4l2loopback-driver



EXPECTED OUTCOME: 
  
Expected  Shell function do_install to finish successfully

ERROR SNIPPET:

| NOTE: make -j 8 KERNEL_SRC=/workdir/tmp/work-shared/qemux86/kernel-source KERNEL_DIR=/workdir/tmp/work-shared/qemux86/kernel-source DEPMOD=echo MODLIB=/workdir/tmp/work/qemux86-poky-linux/v4l2loopback-driver/1.0+git999-r0/image/lib/modules/4.10.9-yocto-standard CC=i586-poky-linux-gcc  -fuse-ld=bfd LD=i586-poky-linux-ld.bfd  O=/workdir/tmp/work-shared/qemux86/kernel-build-artifacts install
| ERROR: oe_runmake failed
| make -C /workdir/tmp/work-shared/qemux86/kernel-source M=/workdir/workspace/sources/v4l2loopback-driver modules_install
| make[1]: Entering directory '/workdir/tmp/work-shared/qemux86/kernel-source'
| make[2]: Entering directory '/workdir/tmp/work-shared/qemux86/kernel-build-artifacts'
|   INSTALL /workdir/workspace/sources/v4l2loopback-driver/v4l2loopback.ko
|   DEPMOD  4.10.9-yocto-standard
| make[2]: Leaving directory '/workdir/tmp/work-shared/qemux86/kernel-build-artifacts'
| make[1]: Leaving directory '/workdir/tmp/work-shared/qemux86/kernel-source'
| depmod -a  `uname -r`
| depmod: ERROR: could not open directory /lib/modules/4.3.0-0.bpo.1-amd64: No such file or directory
| depmod: FATAL: could not search modules: No such file or directory
| make: *** [Makefile:48: install] Error 1
| ERROR: Function failed: do_install (log file is located at /workdir/tmp/work/qemux86-poky-linux/v4l2loopback-driver/1.0+git999-r0/temp/log.do_install.2892)

reproducibility: executed the step 3 times on the same container. Created a different container with poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh. 

When reproduced in a non-container environment it did not fail.
Comment 1 Todor Minchev 2017-04-27 22:17:47 UTC 
This is a bug in the kernel module Makefile. Pull request sent upstream:

https://github.com/umlaeute/v4l2loopback/pull/136
Comment 2 brian avery 2017-04-28 19:57:20 UTC 
please send oe patch as well and do the upstream status as detailed on https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Comment 3 Todor Minchev 2017-04-28 22:07:02 UTC 
I don't see a v4l2loopback recipe.
Comment 4 brian avery 2017-05-01 17:01:24 UTC 
Hmm, 
so this isn't a recipe we are building. It comes in when we run something like 
$ bitbake core-image-minimal -c testsdkext 
It is in the meta/lib/oeqa/sdkect/cases/devtool.py test case test_devtool_kernelmodule

The best solution would probably be to pick a different kernel module and use that since the upstream itself is broken. Or send mail to the v4l2loopback people and see if they are responsive.

Adding Paul in case he has other favorite kernel drivers he's tested with this. The smattering I glanced at on github often have "special" instructions to build.
Comment 5 Todor Minchev 2017-05-08 16:17:46 UTC 
Upstream doesn't seem to be very responsive. 
Perhaps the best option is to pick another kernel module.
Comment 6 Todor Minchev 2017-05-11 23:08:13 UTC 
This kernel module seems to be well maintained and sane.

https://github.com/notro/fbtft

I have also updated the devtool test in the extensible sdk(testsdkext).

https://lists.yoctoproject.org/pipermail/yocto/2017-May/036041.html