On Sun, 16 Mar 2025 at 11:20, kernel test robot <lkp@xxxxxxxxx> wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git kbuild > head: e3de46f775ec29a17f671523798c28222a4ce818 > commit: cac289e2b2b0909b52c0a694c4469a9ad9f03764 [25/35] kbuild: Create intermediate vmlinux build with relocations preserved > config: i386-buildonly-randconfig-001-20250316 (https://download.01.org/0day-ci/archive/20250316/202503161833.ytx1ivfu-lkp@xxxxxxxxx/config) > compiler: clang version 20.1.0 (https://github.com/llvm/llvm-project 24a30daaa559829ad079f2ff7f73eb4e18095f88) > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250316/202503161833.ytx1ivfu-lkp@xxxxxxxxx/reproduce) > > If you fix the issue in a separate patch/commit (i.e. not just a new version of > the same patch/commit), kindly add following tags > | Reported-by: kernel test robot <lkp@xxxxxxxxx> > | Closes: https://lore.kernel.org/oe-kbuild-all/202503161833.ytx1ivfu-lkp@xxxxxxxxx/ > > All errors (new ones prefixed by >>): > > >> FAILED cannot open vmlinux: No such file or directory > We need the below - Masahiro, would you like me to send this is a follow-up patch? --- a/scripts/link-vmlinux.sh +++ b/scripts/link-vmlinux.sh @@ -185,7 +185,7 @@ cleanup() { rm -f .btf.* rm -f System.map - rm -f vmlinux + rm -f "${VMLINUX}" rm -f vmlinux.map } @@ -288,12 +288,12 @@ vmlinux_link "${VMLINUX}" # fill in BTF IDs if is_enabled CONFIG_DEBUG_INFO_BTF; then - info BTFIDS vmlinux + info BTFIDS "${VMLINUX}" RESOLVE_BTFIDS_ARGS="" if is_enabled CONFIG_WERROR; then RESOLVE_BTFIDS_ARGS=" --fatal_warnings " fi - ${RESOLVE_BTFIDS} ${RESOLVE_BTFIDS_ARGS} vmlinux + ${RESOLVE_BTFIDS} ${RESOLVE_BTFIDS_ARGS} "${VMLINUX}" fi mksysmap "${VMLINUX}" System.map
