The Linux Kernel Mailing List
 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>, Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	James Clark <james.clark@linaro.org>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] perf docs: Mark the Android document as obsolete
Date: Mon, 15 Jul 2024 21:10:35 +0100	[thread overview]
Message-ID: <8aca17e0-23fe-4b5c-9209-ff8ef1463314@arm.com> (raw)
In-Reply-To: <CAP-5=fUGJmOr9XcsVWWCREjr1A7rUFaMk0VPkQAKDAEjTLKJVQ@mail.gmail.com>

On 7/15/2024 8:44 PM, Ian Rogers wrote:

[...]

> So we're cross-compiling in bazel, so it is a different set up than
> the makefiles - I'm happy to work to share the bazel set up if other
> people care. I'm having a play to see if I can get the Makefile
> working, my first attempts are clearly mixing x86 code into the
> supposedly arm64 build, which would appear to be more of a build
> system rather than code problem.

Thanks!

I don't have knowledge for Bazel build system, but it surprised me a bit that
the build system doesn't use the makefiles in Perf.

I think it is the right way to fix makefiles in Perf for cross building with
LLVM/Clang. I would like hold on the Android document updating - once the
building is fixed, we will have better knowledge for building perf on Android.

Thanks,
Leo

  parent reply	other threads:[~2024-07-15 20:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 14:33 [PATCH v2] perf docs: Mark the Android document as obsolete Leo Yan
2024-07-15 15:29 ` James Clark
2024-07-15 17:17 ` Ian Rogers
2024-07-15 19:31   ` Leo Yan
2024-07-15 19:44     ` Ian Rogers
2024-07-15 20:06       ` Ian Rogers
2024-07-15 20:36         ` Leo Yan
2024-07-15 21:21           ` Ian Rogers
2024-07-16 10:06             ` Leo Yan
2024-07-16 13:30               ` Ian Rogers
2024-07-16 13:49                 ` Leo Yan
2024-07-16 15:05                   ` Ian Rogers
2024-07-16 15:41                     ` Leo Yan
2024-07-15 20:10       ` Leo Yan [this message]
2024-07-16  9:10   ` James Clark
2024-07-16 10:40     ` Leo Yan

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=8aca17e0-23fe-4b5c-9209-ff8ef1463314@arm.com \
    --to=leo.yan@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=justinstitt@google.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=morbo@google.com \
    --cc=namhyung@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.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