From: kernel test robot <yujie.liu@intel.com>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
<llvm@lists.linux.dev>,
"Linux Memory Management List" <linux-mm@kvack.org>
Subject: clang: error: unknown argument '-static-libasan'; did you mean '-static-libsan'?
Date: Tue, 16 Apr 2024 15:42:04 +0800 [thread overview]
Message-ID: <202404141807.LgsqXPY5-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 7efd0a74039fb6b584be2cb91c1d0ef0bd796ee1
commit: c652df8a4a9d7853fa1100b244024fd6f1a9c18a selftests: link libasan statically for tests with -fsanitize=address
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
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 <yujie.liu@intel.com>
| Closes: https://lore.kernel.org/r/202404141807.LgsqXPY5-lkp@intel.com/
All errors (new ones prefixed by >>):
# tools/testing/selftests/fchmodat2$ make CC=clang
clang -Wall -O2 -g -fsanitize=address -fsanitize=undefined -static-libasan -isystem usr/include fchmodat2_test.c -o tools/testing/selftests/fchmodat2/fchmodat2_test
clang: error: unknown argument '-static-libasan'; did you mean '-static-libsan'?
make: *** [../lib.mk:181: tools/testing/selftests/fchmodat2/fchmodat2_test] Error 1
# tools/testing/selftests/openat2$ make CC=clang
clang -Wall -O2 -g -fsanitize=address -fsanitize=undefined -static-libasan openat2_test.c helpers.c helpers.h -o tools/testing/selftests/openat2/openat2_test
clang: error: unknown argument '-static-libasan'; did you mean '-static-libsan'?
clang: error: cannot specify -o when generating multiple output files
make: *** [../lib.mk:181: tools/testing/selftests/openat2/openat2_test] Error 1
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-04-16 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 7:42 kernel test robot [this message]
2024-04-16 14:33 ` Ryan Roberts
2024-04-16 14:42 ` Arnd Bergmann
2024-04-16 14:55 ` Ryan Roberts
2024-04-17 15:11 ` Ryan Roberts
2024-04-17 15:23 ` Arnd Bergmann
2024-04-17 15:52 ` Ryan Roberts
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=202404141807.LgsqXPY5-lkp@intel.com \
--to=yujie.liu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ryan.roberts@arm.com \
/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