https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: media-tv/v4l-dvb-saa716x-0.0.1_p20170225-r5 calls commands that do not exist. Discovered on: amd64 (internal ref: ci) NOTE: Please look for 'command not found' and/or 'no such file or directory'.
Created attachment 780524 [details] build.log build log and emerge --info
Error(s) that match a know pattern in addition to what has been reported in the summary: /bin/sh: line 1: /sbin/lsmod: No such file or directory make[1]: *** No rule to make target 'modules'. Stop. /var/tmp/portage/media-tv/v4l-dvb-saa716x-0.0.1_p20170225-r5/temp/environment: line 1726: cd: /usr/src/linux: No such file or directory
Comment on attachment 780524 [details] build.log Hi, I have no definite idea what's going wrong with this automated test. The package you are testing here produces some kernel modules, fitting into the currently "eselect"ed kernel, or in other words the kernel sources where /usr/src/linux is pointing to. First, I see the tinderbox looks like running on kernel 4.19.174. Then I see in the emerge history of the test that sys-kernel/gentoo-sources-5.18.0 has been merged and most probably not "eselected" and configured. Next, in the build.log of the package, there is stated that /kernel-5.4.114 sources have been detected. Some lines later, I read "No version yet, using 4.19.174-gentoo". All in all I assume that this kind of tinderbox compile environment does not look very suitable for kernel module packages testing. And I tend to mark this Bug as "wontfix". What's your opinion?
(In reply to Martin Dummer from comment #3) > What's your opinion? my opinion is that we have /bin/lsmod provided by sys-apps/kmod while the build systems looks for /sbin/lsmod
