From: kernel test robot <lkp@intel.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: [mchehab-media-next:master 314/316] scripts/Makefile.build:44: drivers/media/platform/nvidia/Makefile: No such file or directory
Date: Mon, 14 Mar 2022 00:37:49 +0800 [thread overview]
Message-ID: <202203140022.R4erbrkI-lkp@intel.com> (raw)
tree: git://linuxtv.org/mchehab/media-next.git master
head: 9d8c4cc1be6c37e66662141f1a3ebc8b54cb8dae
commit: 63533d0167e608fde8c40a7579e6ac22b1ffdfbc [314/316] media: platform: Create vendor/{Makefile,Kconfig} files
config: arc-randconfig-r043-20220313 (https://download.01.org/0day-ci/archive/20220314/202203140022.R4erbrkI-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add mchehab-media-next git://linuxtv.org/mchehab/media-next.git
git fetch --no-tags mchehab-media-next master
git checkout 63533d0167e608fde8c40a7579e6ac22b1ffdfbc
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> scripts/Makefile.build:44: drivers/media/platform/nvidia/Makefile: No such file or directory
>> make[5]: *** No rule to make target 'drivers/media/platform/nvidia/Makefile'.
make[5]: Failed to remake makefile 'drivers/media/platform/nvidia/Makefile'.
vim +44 scripts/Makefile.build
20a468b51325b3 Sam Ravnborg 2006-01-22 40
2a691470345a00 Sam Ravnborg 2005-07-25 41 # The filename Kbuild has precedence over Makefile
db8c1a7b2ca25f Sam Ravnborg 2005-07-27 42 kbuild-dir := $(if $(filter /%,$(src)),$(src),$(srctree)/$(src))
0c53c8e6eb456c Sam Ravnborg 2007-10-14 43 kbuild-file := $(if $(wildcard $(kbuild-dir)/Kbuild),$(kbuild-dir)/Kbuild,$(kbuild-dir)/Makefile)
0c53c8e6eb456c Sam Ravnborg 2007-10-14 @44 include $(kbuild-file)
^1da177e4c3f41 Linus Torvalds 2005-04-16 45
:::::: The code at line 44 was first introduced by commit
:::::: 0c53c8e6eb456cde30f2305421c605713856abc8 kbuild: check for wrong use of CFLAGS
:::::: TO: Sam Ravnborg <sam@neptun.(none)>
:::::: CC: Sam Ravnborg <sam@neptun.(none)>
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-13 16:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202203140022.R4erbrkI-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox