linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
	Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	James Clark <james.clark@linaro.org>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	llvm@lists.linux.dev, linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 0/8] perf build: Support building with Clang
Date: Wed, 1 Oct 2025 16:22:17 +0100	[thread overview]
Message-ID: <20251001152217.GQ7985@e132581.arm.com> (raw)
In-Reply-To: <aN044EY-Ds9-E6iz@x1>

On Wed, Oct 01, 2025 at 11:21:20AM -0300, Arnaldo Carvalho de Melo wrote:
> On Tue, Sep 30, 2025 at 05:54:48PM +0100, Leo Yan wrote:
> > This series adds support for building perf with Clang, following the
> > discussion in [1]. Because the Android NDK uses Clang by default,
> > enabling Clang builds naturally covers Android as well.
> > 
> > The series is organized as follows:
> > 
> >   - Patches 1–2: Fix two bugs found with Clang.
> >   - Patches 3–6: Correct CROSS_ARCH and dismiss Clang build warnings.
> >   - Patches 7–8: Enable Clang in the Makefile and update the
> >     documentation.
> > 
> > Testing:
> > 
> >   - Clang 15.0.7 on Ubuntu 22.04.5: native and cross-compiling (aarch64)
> >   - Clang 18.1.3 on Ubuntu 24.04.2: native and cross-compiling (aarch64)
> >   - Android NDK r27d (latest LTS): cross-compiling (aarch64)
> 
>   LD      /tmp/build/perf/util/perf-util-in.o
>   LD      /tmp/build/perf/perf-util-in.o
>   AR      /tmp/build/perf/libperf-util.a
>   CC      /tmp/build/perf/pmu-events/pmu-events.o
>   LD      /tmp/build/perf/pmu-events/pmu-events-in.o
>   AR      /tmp/build/perf/libpmu-events.a
>   LINK    /tmp/build/perf/perf
> make: Leaving directory '/git/perf-6.17.0-rc6/tools/perf'
> + rm -rf /tmp/build/perf
> + mkdir /tmp/build/perf
> + make 'ARCH=' 'CROSS_COMPILE=' 'EXTRA_CFLAGS=' -C tools/perf 'O=/tmp/build/perf' 'CC=clang'
> make: Entering directory '/git/perf-6.17.0-rc6/tools/perf'
>   BUILD:   Doing 'make -j28' parallel build
> Makefile.config:494: *** No gnu/libc-version.h found, please install glibc-dev[el].  Stop.
> make[1]: *** [Makefile.perf:289: sub-make] Error 2
> make: *** [Makefile:76: all] Error 2
> make: Leaving directory '/git/perf-6.17.0-rc6/tools/perf'
> + exit 1
> toolsbuilder@five:~$ cat dm.log/alpine\:3.22

A quick look: the build cannot find both libelf (feature-libelf=0) and
glibc (feature-glibc=0), thus lead to build failure. It is good to
know what the reason for the feature building failures:

  tools/perf/feature/test-libelf.make.output
  tools/perf/feature/test-glibc.make.output

I am not surprised for the failure of libelf (this is common case
that the package is not installed by default in a distro), but it is a
bit confused for the glibc feature failure.

It seems the issue occurs on Alpine 3.22, but the highest version
supported in container-build is 3.21 [1]. Could you confirm whether
the issue reproduces on other distros or versions?

Thanks,
Leo

[1] https://github.com/acmel/linux-tools-container-builds/tree/main/alpine

  reply	other threads:[~2025-10-01 15:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 16:54 [PATCH v2 0/8] perf build: Support building with Clang Leo Yan
2025-09-30 16:54 ` [PATCH v2 1/8] tools build: Align warning options with perf Leo Yan
2025-09-30 16:54 ` [PATCH v2 2/8] perf python: split Clang options when invoking Popen Leo Yan
2025-09-30 16:54 ` [PATCH v2 3/8] perf: build: Correct CROSS_ARCH for clang Leo Yan
2025-09-30 16:54 ` [PATCH v2 4/8] perf test coresight: Dismiss clang warning for memcpy thread Leo Yan
2025-09-30 16:54 ` [PATCH v2 5/8] perf test coresight: Dismiss clang warning for thread loop Leo Yan
2025-09-30 16:54 ` [PATCH v2 6/8] perf test coresight: Dismiss clang warning for unroll loop thread Leo Yan
2025-09-30 16:54 ` [PATCH v2 7/8] perf build: Support build with clang Leo Yan
2025-09-30 16:54 ` [PATCH v2 8/8] perf docs: Document building with Clang Leo Yan
2025-09-30 18:14 ` [PATCH v2 0/8] perf build: Support " Ian Rogers
2025-10-01 13:45   ` Arnaldo Carvalho de Melo
2025-10-01 14:21 ` Arnaldo Carvalho de Melo
2025-10-01 15:22   ` Leo Yan [this message]
2025-10-01 18:25     ` Arnaldo Carvalho de Melo
2025-10-01 18:32       ` Leo Yan
2025-10-01 20:20         ` Leo Yan
2025-10-02 17:43           ` 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=20251001152217.GQ7985@e132581.arm.com \
    --to=leo.yan@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=namhyung@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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).