[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAO9wTFiH-wrvAgwUhPH3=a-K5HDODzuqe1+4D+aigxe5J_dq6Q@mail.gmail.com>
Date: Wed, 23 Jul 2025 10:00:13 +0530
From: Suchit K <suchitkarunakaran@...il.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: peterz@...radead.org, mingo@...hat.com, acme@...nel.org,
mark.rutland@....com, alexander.shishkin@...ux.intel.com, jolsa@...nel.org,
irogers@...gle.com, adrian.hunter@...el.com, kan.liang@...ux.intel.com,
linux-perf-users@...r.kernel.org, sesse@...gle.com, charlie@...osinc.com,
linux-kernel@...r.kernel.org, linux-kernel-mentees@...ts.linux.dev,
skhan@...uxfoundation.org
Subject: Re: [PATCH] perf tests: Fix lib path detection for non-x86 architectures
>
> I'd be intrusive if we create a new symlink. Probably we need to check
> if there's lib64 directory first and use it for 64 bit build. But I
> feel like this needs more testing.
>
> Can you share what's the problem exactly?
>
> Thanks,
> Namhyung
>
Yeah I agree it needs more testing. And yes we can check if the lib64
folder exists and then create a symlink. If there's no lib64 folder,
we can create a symlink named lib64 to the lib folder. I assume this
will cover most of the architectures since the lib folder existed in
almost all the architectures that I tested.
Powered by blists - more mailing lists