linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Roberts <ryan.roberts@arm.com>
To: kernel test robot <yujie.liu@intel.com>, Arnd Bergmann <arnd@arndb.de>
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: Re: clang: error: unknown argument '-static-libasan'; did you mean '-static-libsan'?
Date: Tue, 16 Apr 2024 15:33:00 +0100	[thread overview]
Message-ID: <31b4e05d-62c6-44cd-8038-7ac8d21320c3@arm.com> (raw)
In-Reply-To: <202404141807.LgsqXPY5-lkp@intel.com>

+ Arnd

On 16/04/2024 08:42, kernel test robot wrote:
> 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
> 

Hi Arnd,

This change went in quite a while ago and is on;y just blowing up. I saw your
comment in another thread [1] that Andrew merged your change to set -Wextra.
Perhaps that's what has caused this to show up only now? *although I don't
actually see -Wextra in the command line).

I guess the problem is that `-static-libasan` is only supported by gcc. But I'm
Makefile-illiterate. Can anyone advise on what's the best way to make this
argument gcc-only?

Thanks,
Ryan

[1]
https://lore.kernel.org/linux-mm/53d194db-c7d4-4026-9fbb-3b41de545849@app.fastmail.com/


  reply	other threads:[~2024-04-16 14:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16  7:42 kernel test robot
2024-04-16 14:33 ` Ryan Roberts [this message]
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=31b4e05d-62c6-44cd-8038-7ac8d21320c3@arm.com \
    --to=ryan.roberts@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yujie.liu@intel.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