public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Maciej Wieczor-Retman" <maciej.wieczor-retman@intel.com>,
	"Christian Brauner" <brauner@kernel.org>,
	"Alexey Gladkov" <legion@kernel.org>,
	"Valentin Obst" <kernel@valentinobst.de>,
	linux-kselftest@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	llvm@lists.linux.dev, "Ryan Roberts" <ryan.roberts@arm.com>,
	"Shuah Khan" <shuah@kernel.org>
Subject: Re: [PATCH 1/2] selftests/openat2: fix clang build failures: -static-libasan, LOCAL_HDRS
Date: Wed, 29 May 2024 21:35:20 -0700	[thread overview]
Message-ID: <00ba2d8c-6b0f-46f4-bd19-bce19842c356@nvidia.com> (raw)
In-Reply-To: <1aec9470-9af2-4113-9cbb-9930ccd92a0b@collabora.com>

On 5/29/24 8:58 PM, Muhammad Usama Anjum wrote:
> On 5/10/24 10:56 PM, John Hubbard wrote:
>> On 5/10/24 4:52 AM, Ryan Roberts wrote:
>>> On 04/05/2024 05:43, John Hubbard wrote:
>> ...
>> In Make, the arguments to functions include *all* spaces, so it's good
>> practice to not add spaces in most function calls, unless they are
>> definitely desired.
>>
>> Also, you only ever want one of those $(CC) options, so saying so is a
>> nice touch. Neither of these is a functional issue in [2], but you could
>> do this on top of the patch (I'm only showing the openat2 case):
> I was building with CC=clang and build was still failing. We should be able
> to build by CC=clang and LLVM=1 both. It seems like patches still haven't
> been accepted. Let's get a v2 out to fix this.
> 

Yes, these are about next on the list, and I expect to post a v2 or its moral
equivalent tomorrow or the next day at the latest.

For the CC=clang vs. LLVM=1 issue in particular, I've already posted a
fix, please see my "[PATCH 0/2] selftests/lib.mk: LLVM=1, CC=clang, and
warnings" [1] that went out just yesterday.

[1] https://lore.kernel.org/20240529020842.127275-1-jhubbard@nvidia.com

thanks,
-- 
John Hubbard
NVIDIA


      reply	other threads:[~2024-05-30  4:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04  4:43 [PATCH 1/2] selftests/openat2: fix clang build failures: -static-libasan, LOCAL_HDRS John Hubbard
2024-05-04  4:43 ` [PATCH 2/2] selftests/fchmodat2: fix clang build failure due to -static-libasan John Hubbard
2024-05-07  7:45 ` [PATCH 1/2] selftests/openat2: fix clang build failures: -static-libasan, LOCAL_HDRS Ryan Roberts
2024-05-07 16:19   ` John Hubbard
2024-05-07 16:34     ` Ryan Roberts
2024-05-07 16:47       ` John Hubbard
2024-05-07 16:56         ` Ryan Roberts
2024-05-10 11:52 ` Ryan Roberts
2024-05-10 17:56   ` John Hubbard
2024-05-10 18:22     ` John Hubbard
2024-05-11 17:19       ` Ryan Roberts
2024-05-30  3:58     ` Muhammad Usama Anjum
2024-05-30  4:35       ` John Hubbard [this message]

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=00ba2d8c-6b0f-46f4-bd19-bce19842c356@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=kernel@valentinobst.de \
    --cc=legion@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=maciej.wieczor-retman@intel.com \
    --cc=ryan.roberts@arm.com \
    --cc=shuah@kernel.org \
    --cc=usama.anjum@collabora.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