public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@arm.com>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	James Clark <james.clark@arm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	Nick Terrell <terrelln@fb.com>,
	Thomas Richter <tmricht@linux.ibm.com>,
	Quentin Monnet <qmo@kernel.org>,
	Changbin Du <changbin.du@huawei.com>,
	Fangrui Song <maskray@google.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Guilherme Amadio <amadio@gentoo.org>
Subject: Re: [PATCH v2 6/6] perf docs: Document cross compilation
Date: Tue, 25 Jun 2024 19:16:18 +0100	[thread overview]
Message-ID: <763864f4-e370-4e0d-a4ee-cbff41ad5c08@arm.com> (raw)
In-Reply-To: <CAP-5=fVqJWGWbrddyqAhUp6afG3AX61ekNr3Mpe6u=wYaeeCcg@mail.gmail.com>



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

      parent reply	other threads:[~2024-06-25 18:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10  9:54 [PATCH v2 0/6] perf: build: Fix cross compilation Leo Yan
2024-06-10  9:54 ` [PATCH v2 1/6] perf: build: Setup PKG_CONFIG_LIBDIR for " Leo Yan
2024-06-21 23:18   ` Namhyung Kim
2024-06-25 17:08     ` Leo Yan
2024-06-10  9:54 ` [PATCH v2 2/6] perf: build: Set Python configuration " Leo Yan
2024-06-10  9:54 ` [PATCH v2 3/6] perf: build: Only link libebl.a for old libdw Leo Yan
2024-06-21 23:40   ` Namhyung Kim
2024-06-25 18:09     ` Leo Yan
2024-06-10  9:54 ` [PATCH v2 4/6] perf: build: Link lib 'lzma' for static build Leo Yan
2024-06-10  9:54 ` [PATCH v2 5/6] perf: build: Link lib 'zstd' " Leo Yan
2024-06-10  9:54 ` [PATCH v2 6/6] perf docs: Document cross compilation Leo Yan
     [not found]   ` <CAP-5=fVqJWGWbrddyqAhUp6afG3AX61ekNr3Mpe6u=wYaeeCcg@mail.gmail.com>
2024-06-25 18:16     ` Leo Yan [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=763864f4-e370-4e0d-a4ee-cbff41ad5c08@arm.com \
    --to=leo.yan@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=amadio@gentoo.org \
    --cc=changbin.du@huawei.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maskray@google.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=qmo@kernel.org \
    --cc=terrelln@fb.com \
    --cc=tmricht@linux.ibm.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