From: Leo Yan <leo.yan@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Leo Yan <leo.yan@arm.com>, Thomas Richter <tmricht@linux.ibm.com>,
James Clark <james.clark@linaro.org>,
amadio@gentoo.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: [PATCH v5 0/6] perf: build: Fix cross compilation
Date: Wed, 17 Jul 2024 09:22:05 +0100 [thread overview]
Message-ID: <20240717082211.524826-1-leo.yan@arm.com> (raw)
This patch series fixes cross compilation issues.
The first patch sets the package path if the package configuration path
is not specified. This helps the compiler to find the architecture's
package in a Multiarch system.
The patch 02 sets the Python configuration path and renames the .so to
The patches 03, 04 and 05 fix the static build failures.
The patch 06 adds document for how to cross compile.
Changes from v4:
- Polished patch 06 for removing redundant sentences.
Changes from v3:
- Added more completed comments and logs for PKG_CONFIG_SYSROOT_DIR.
(Namhyung)
- Didn't include the patch 07 for "perf docs: Remove the Android cross
building document" in this version, which will be sent out separately.
(Namhyung/James)
Changes from v2:
- Reordered lib paths for PKG_CONFIG_LIBDIR. (Namhyung)
- Verified the Android NDK and based on the testing result to remove the
file android.txt. (Ian)
Changes from v1:
- Kept the cross-compile-pkg-config if it is available. (Namhyung)
- Removed the patch 02 for fixing pkg-config path for libtraceevent, as
this will be resolved in Guilherme Amadio's patch "perf build: Use
pkg-config for feature check for libtrace{event,fs}".
- Added patch 06 for document.
Leo Yan (6):
perf: build: Setup PKG_CONFIG_LIBDIR for cross compilation
perf: build: Set Python configuration for cross compilation
perf: build: Only link libebl.a for old libdw
perf: build: Link lib 'lzma' for static build
perf: build: Link lib 'zstd' for static build
perf docs: Document cross compilation
tools/build/feature/Makefile | 53 ++++++++++++++++++++++++------
tools/perf/Documentation/Build.txt | 28 ++++++++++++++++
tools/perf/Makefile.config | 20 ++++++++++-
tools/perf/Makefile.perf | 27 ++++++++++++++-
4 files changed, 116 insertions(+), 12 deletions(-)
--
2.34.1
next reply other threads:[~2024-07-17 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 8:22 Leo Yan [this message]
2024-07-17 8:22 ` [PATCH v5 1/6] perf: build: Setup PKG_CONFIG_LIBDIR for cross compilation Leo Yan
2024-07-17 8:22 ` [PATCH v5 2/6] perf: build: Set Python configuration " Leo Yan
2024-07-17 8:22 ` [PATCH v5 3/6] perf: build: Only link libebl.a for old libdw Leo Yan
2024-07-17 8:22 ` [PATCH v5 4/6] perf: build: Link lib 'lzma' for static build Leo Yan
2024-07-17 8:22 ` [PATCH v5 5/6] perf: build: Link lib 'zstd' " Leo Yan
2024-07-17 8:22 ` [PATCH v5 6/6] perf docs: Document cross compilation Leo Yan
2024-07-17 15:22 ` [PATCH v5 0/6] perf: build: Fix " Ian Rogers
2024-07-25 6:53 ` Leo Yan
2024-07-26 1:27 ` Namhyung Kim
2024-07-26 12:37 ` Arnaldo Carvalho de Melo
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=20240717082211.524826-1-leo.yan@arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=amadio@gentoo.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).