* [masahiroy-kbuild:kbuild 25/35] FAILED cannot open vmlinux: No such file or directory
@ 2025-03-16 10:19 kernel test robot
2025-03-16 14:09 ` Ard Biesheuvel
0 siblings, 1 reply; 3+ messages in thread
From: kernel test robot @ 2025-03-16 10:19 UTC (permalink / raw)
To: Ard Biesheuvel; +Cc: llvm, oe-kbuild-all, linux-kbuild, Masahiro Yamada
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@intel.com/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@intel.com/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@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202503161833.ytx1ivfu-lkp@intel.com/
All errors (new ones prefixed by >>):
>> FAILED cannot open vmlinux: No such file or directory
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [masahiroy-kbuild:kbuild 25/35] FAILED cannot open vmlinux: No such file or directory
2025-03-16 10:19 [masahiroy-kbuild:kbuild 25/35] FAILED cannot open vmlinux: No such file or directory kernel test robot
@ 2025-03-16 14:09 ` Ard Biesheuvel
2025-03-16 15:27 ` Masahiro Yamada
0 siblings, 1 reply; 3+ messages in thread
From: Ard Biesheuvel @ 2025-03-16 14:09 UTC (permalink / raw)
To: kernel test robot; +Cc: llvm, oe-kbuild-all, linux-kbuild, Masahiro Yamada
On Sun, 16 Mar 2025 at 11:20, kernel test robot <lkp@intel.com> 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@intel.com/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@intel.com/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@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202503161833.ytx1ivfu-lkp@intel.com/
>
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [masahiroy-kbuild:kbuild 25/35] FAILED cannot open vmlinux: No such file or directory
2025-03-16 14:09 ` Ard Biesheuvel
@ 2025-03-16 15:27 ` Masahiro Yamada
0 siblings, 0 replies; 3+ messages in thread
From: Masahiro Yamada @ 2025-03-16 15:27 UTC (permalink / raw)
To: Ard Biesheuvel; +Cc: kernel test robot, llvm, oe-kbuild-all, linux-kbuild
On Sun, Mar 16, 2025 at 11:09 PM Ard Biesheuvel <ardb@kernel.org> wrote:
>
> On Sun, 16 Mar 2025 at 11:20, kernel test robot <lkp@intel.com> 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@intel.com/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@intel.com/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@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202503161833.ytx1ivfu-lkp@intel.com/
> >
> > 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}"
This is wrong because the target vmlinux is not passed
during 'make clean'.
https://github.com/torvalds/linux/blob/v6.14-rc5/Makefile#L1583
> 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}"
These two changes are correct.
I will squash.
--
Best Regards
Masahiro Yamada
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-03-16 15:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-03-16 10:19 [masahiroy-kbuild:kbuild 25/35] FAILED cannot open vmlinux: No such file or directory kernel test robot
2025-03-16 14:09 ` Ard Biesheuvel
2025-03-16 15:27 ` Masahiro Yamada
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.