From: Namhyung Kim <namhyung@kernel.org>
To: pgnmirror <vacacax16@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
linux-perf-users@vger.kernel.org,
zntsproj <vseokaktusah7@gmail.com>
Subject: Re: [PATCH v2] tools/perf/tests/make: use IS_64_BIT for generic lib dir
Date: Fri, 31 Oct 2025 12:04:20 -0700 [thread overview]
Message-ID: <aQUINHg0w8_BwtG4@google.com> (raw)
In-Reply-To: <20251031151114.5642-1-vacacax16@gmail.com>
On Fri, Oct 31, 2025 at 06:11:14PM +0300, pgnmirror wrote:
> Use the IS_64_BIT flag to set the lib directory generically for all architectures.
> Previously, this logic was hardcoded for x86/x86_64 only.
>
> Signed-off-by: zntsproj <vseokaktusah7@gmail.com>
> ---
> tools/perf/tests/make | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/tests/make b/tools/perf/tests/make
> index b650ce886..64066e011 100644
> --- a/tools/perf/tests/make
> +++ b/tools/perf/tests/make
> @@ -53,9 +53,8 @@ endif
>
> include $(srctree)/tools/scripts/Makefile.arch
>
> -# FIXME looks like x86 is the only arch running tests ;-)
> -# we need some IS_(32/64) flag to make this generic
> -ifeq ($(ARCH)$(IS_64_BIT), x861)
> +# use IS_64_BIT to select lib/lib64 generically for all architectures
> +ifeq ($(IS_64_BIT), 1)
IIRC last time we checked this, some arch/distro didn't have lib64
directory on 64-bit systems. Are you sure if it'd work on them or do
you have any real problem with this?
Thanks,
Namhyung
> lib = lib64
> else
> lib = lib
> --
> 2.51.2
>
prev parent reply other threads:[~2025-10-31 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 15:11 [PATCH v2] tools/perf/tests/make: use IS_64_BIT for generic lib dir pgnmirror
2025-10-31 19:04 ` Namhyung Kim [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=aQUINHg0w8_BwtG4@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=vacacax16@gmail.com \
--cc=vseokaktusah7@gmail.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;
as well as URLs for NNTP newsgroup(s).