Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
Cc: <buildroot@buildroot.org>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Olivier Benjamin" <olivier.benjamin@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/linux-tools: perf: build with libtraceevent support when it is selected
Date: Thu, 26 Jun 2025 10:46:10 +0200	[thread overview]
Message-ID: <DAWC0TAMO2HJ.11A5HZP7IY369@bootlin.com> (raw)
In-Reply-To: <20250626100242.27ab1407@booty>

Hi Luca,

>> It is worth noting that there is a bug in perf makefile kernel that
>> affects many kernel versions (up to 6.10) and that prevents perf from
>> building correctly when enabling libtraceevent support (see 440cf77625e3
>> ("perf: build: Setup PKG_CONFIG_LIBDIR for cross compilation") in
>> linux).
>
> Thanks for the research!
>
> And apparently the mentioned commit was applied in 6.11 and not
> backported to 6.10 and previous stable releases

Yes, you are right, my mistake.

> Shouldn't it be backported? This looks like a fix, doesn't it?

Indeed. The original author on kernel side did not bring any Fixes tag so
it may have slipped through the stable kernels, but I can try to submit it
for current stable/LTS kernels.

>> Should the libtraceevent then be explicitely enabled by the
>> user, rather than automatically enabling it when libtraceevent package
>> is selected ?
>
> Should the fix be backported to the currently-supported stable kernel
> versions, I'd say we can automatically enable libtraceevent support.
> Otherwise I'm not sure... Mentioning the issue and pointing to the fix
> commit in the Kconfig help text is another option.

Mentioning the kernel version fixing the issue in the KConfig help sounds
relevant, but maybe having the exact kernel commit only in the BR commit
description is enough ? If so, I can prepare a v2 with the updated Kconfig.

Thanks

Alexis

-- 
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2025-06-26  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 20:54 [Buildroot] [PATCH] package/linux-tools: perf: build with libtraceevent support when it is selected Alexis Lothoré via buildroot
2025-06-26  8:02 ` Luca Ceresoli via buildroot
2025-06-26  8:46   ` Alexis Lothoré via buildroot [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=DAWC0TAMO2HJ.11A5HZP7IY369@bootlin.com \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=olivier.benjamin@bootlin.com \
    --cc=thomas.petazzoni@bootlin.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