From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: <llvm@lists.linux.dev>, <oe-kbuild-all@lists.linux.dev>,
<linux-kbuild@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: [masahiroy-kbuild:kbuild 15/20] error: Unrecognized option: 'remap-path-prefix'
Date: Thu, 13 Mar 2025 08:51:28 +0800 [thread overview]
Message-ID: <Z9IsEPOnC+MGSAEA@rli9-mobl> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git kbuild
head: bc5431693696b3f928b0b7acf8d7a120127db7a4
commit: 6b5747d07138f8109b1a150830f1d138de146ac2 [15/20] kbuild, rust: use -fremap-path-prefix to make paths relative
:::::: branch date: 24 hours ago
:::::: commit date: 30 hours ago
config: x86_64-buildonly-randconfig-004-20250312 (https://download.01.org/0day-ci/archive/20250313/202503130111.NH87la6s-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250313/202503130111.NH87la6s-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/r/202503130111.NH87la6s-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error: Unrecognized option: 'remap-path-prefix'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-03-13 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 0:51 kernel test robot [this message]
2025-03-15 7:45 ` [masahiroy-kbuild:kbuild 15/20] error: Unrecognized option: 'remap-path-prefix' Masahiro Yamada
2025-03-15 8:39 ` Miguel Ojeda
2025-03-15 10:15 ` Masahiro Yamada
2025-03-15 15:53 ` Miguel Ojeda
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=Z9IsEPOnC+MGSAEA@rli9-mobl \
--to=lkp@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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