[<prev] [next>] [day] [month] [year] [list]
Message-ID: <763864f4-e370-4e0d-a4ee-cbff41ad5c08@arm.com>
Date: Tue, 25 Jun 2024 19:16:18 +0100
From: Leo Yan <leo.yan@....com>
To: Ian Rogers <irogers@...gle.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Namhyung Kim <namhyung@...nel.org>, James Clark <james.clark@....com>,
Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>,
"Liang, Kan" <kan.liang@...ux.intel.com>, Nick Terrell <terrelln@...com>,
Thomas Richter <tmricht@...ux.ibm.com>, Quentin Monnet <qmo@...nel.org>,
Changbin Du <changbin.du@...wei.com>, Fangrui Song <maskray@...gle.com>,
linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
Guilherme Amadio <amadio@...too.org>
Subject: Re: [PATCH v2 6/6] perf docs: Document cross compilation
On 6/10/24 19:43, Ian Rogers wrote:
>
> Records the commands for cross compilation with two methods.
>
> The first method relies on Multiarch. The second approach is to
> explicitly
> specify the PKG_CONFIG variables, which is widely used in build system
> (like Buildroot, Yocto, etc).
>
>
> There is also:
> https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/tree/tools/perf/Documentation/android.txt?h=perf-tools-next
> it looks very crufty, not least as it is referringĀ to 32-bit builds
>
> Could this be refreshed or deleted?
Yeah, the doc is quite old.
Actually, this patch series is to support static building, I assume a
main usage case is to use the static building binary for Android.
I will give a try for building perf with Android NDK. I will base on my
test result to update the file android.txt or remove it.
Thanks
Leo
Powered by blists - more mailing lists