Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: "Julien Olivain" <ju.o@free.fr>
Cc: <buildroot@buildroot.org>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Francis Laniel" <flaniel@linux.microsoft.com>
Subject: Re: [Buildroot] [PATCH] package/pahole: bump to version 1.28
Date: Tue, 15 Apr 2025 23:07:39 +0200	[thread overview]
Message-ID: <D97IPBMKJNQL.1EF4TZDMMBRCA@bootlin.com> (raw)
In-Reply-To: <51a49e9cb3753181d544641efbf14880@free.fr>

Hello Julien,

On Tue Apr 15, 2025 at 7:23 PM CEST, Julien Olivain wrote:
> On 15/04/2025 09:19, Alexis Lothoré via buildroot wrote:
>> On hosts with a recent version of cmake (eg: 4.0.0), builds involving
>> host-pahole fail with the following error:
>> 
>> CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
>>   Compatibility with CMake < 3.5 will be removed from a future version 
>> of
>>   CMake.
>> 
>>   Update the VERSION argument <min> value or use a ...<max> suffix to 
>> tell
>>   CMake that the project does not need compatibility with older 
>> versions.
>> 
>> The issue has already fixed in the upstream project with commit
>> 12ca11281912 ("CMakeLists.txt: Require cmake 3.5 or higher"), which is
>> part of version 1.28.
>> 
>> Upgrade pahole to get rid of this error.
>> 
>> https://git.kernel.org/pub/scm/devel/pahole/pahole.git/tree/NEWS?h=v1.28
>> 
>> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
>
> Applied to master, thanks.
>
> I also added in the commit log your example config which
> reproduces the issue.

Nice, thanks.

In case it has slipped through: as the issue also exists on the current
release branch, do you want me to send a patch targeting the 2025.02.x
branch to backport the upstream patch fixing the issue ? (because I guess
bumping the package version on the release branch is not an option ?)

Thanks,

Alexis
>
> Best regards,
>
> Julien.
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot




-- 
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-04-15 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15  7:19 [Buildroot] [PATCH] package/pahole: bump to version 1.28 Alexis Lothoré via buildroot
2025-04-15 17:23 ` Julien Olivain
2025-04-15 21:07   ` Alexis Lothoré via buildroot [this message]
2025-04-18 10:37     ` Thomas Petazzoni via buildroot
2025-04-18 18:28       ` Alexis Lothoré via buildroot

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=D97IPBMKJNQL.1EF4TZDMMBRCA@bootlin.com \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.com \
    --cc=flaniel@linux.microsoft.com \
    --cc=ju.o@free.fr \
    --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