public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Michel Lind <michel@michel-slm.name>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: Recent tarballs missing some files
Date: Mon, 25 Nov 2024 21:26:34 -0600	[thread overview]
Message-ID: <Z0U/6hbVcLv8mdV4@hyperscale.parallels> (raw)
In-Reply-To: <CA+JHD91LPXRadmVckNMSf-zMNuJsEO1_pk0JC57XdVQczadwgA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2307 bytes --]

Hi Arnaldo,

On Mon, Nov 25, 2024 at 10:50:49PM -0300, Arnaldo Carvalho de Melo wrote:
> On Mon, Nov 25, 2024, 8:50 PM Michel Lind <michel@michel-slm.name> wrote:
> 
> > On Mon, Nov 25, 2024 at 12:08:28PM -0600, Michel Lind wrote:
> > > Hello all,
> > >
> > > Per discussions with acme back at LPC, I'm working on packaging a
> > > standalone perf RPM, initially for the CentOS Hyperscale SIG and
> > > potentially for Fedora later on.
> > >
> > > I noticed that, while perf 6.9.0 builds fine from the source tarball,
> > > more recent versions (at least 6.11 and 6.12) fails due to a missing
> > > header:
> > >
> > > ```
> > > In file included from
> > /builddir/build/BUILD/perf-6.12.0/tools/include/uapi/linux/bpf_perf_event.h:11,
> > >                  from libbpf.c:36:
> > >
> > /builddir/build/BUILD/perf-6.12.0/tools/include/uapi/asm/bpf_perf_event.h:2:10:
> > fatal error: ../../arch/arm64/include/uapi/asm/bpf_perf_event.h: No such
> > file or directory
> > >     2 | #include "../../arch/arm64/include/uapi/asm/bpf_perf_event.h"
> > >       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > compilation terminated.
> > > ```
> > >
> > > I can submit a patch to fix this (and any other missing files), if
> > > someone could point me to where the script is that generates the perf
> > > tarballs.
> > >
> > Update - on digging in this only happens on aarch64 (probably why this
> > was not caught earlier). And it also affects 6.9.0. In all cases the
> > alternatives are either copying in that one header *or* passing
> > NO_LIBBPF=1
> >
> 
> Maybe the case of adding the missing file to:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/tools/perf/MANIFEST
> 
> Look at the other csets for explanation.
> 
> You could also try building with the system 's libbpf, look at:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/perf/Makefile.perf#n120
>

Thank you!

Building with the system libbpf might not be an option when building for
older Enterprise Linux releases, but I'll add that as an option in the
spec for new enough releases.

Best regards,

-- 
 _o) Michel Lind
_( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2024-11-26  3:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 18:08 Recent tarballs missing some files Michel Lind
2024-11-25 23:50 ` Michel Lind
     [not found]   ` <CA+JHD91LPXRadmVckNMSf-zMNuJsEO1_pk0JC57XdVQczadwgA@mail.gmail.com>
2024-11-26  3:26     ` Michel Lind [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=Z0U/6hbVcLv8mdV4@hyperscale.parallels \
    --to=michel@michel-slm.name \
    --cc=arnaldo.melo@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    /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