Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Andrey Nechypurenko <andreynech@gmail.com>
Cc: Alsey Miller <alseycmiller@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/cmake: bump version to 3.22.3
Date: Wed, 11 May 2022 13:06:16 +0300	[thread overview]
Message-ID: <878rr88joi.fsf@tarshish> (raw)
In-Reply-To: <CAOiXNkDBgP=sjS5WEKR58VSgfikBmSV8FmcaQygAPHi-E_Lptw@mail.gmail.com>

Hi Andrey,

On Wed, May 11 2022, Andrey Nechypurenko wrote:
>> On 10/05/2022 17:20, Andrey Nechypurenko wrote:
>> >>> I am just curious if the following patch will be accepted for the
>> >>> upcoming release?
>> >>
>> >> What about bumping it to 3.23.1?
>> >
>> > At the time I submitted the patch (29.03), v.3.22 was the latest one. It
>> > also fixes the bug I was facing. So it is good enough for me and definitely
>> > better than v.3.18 currently used by Buildroot. If you would like to submit
>> > another one for v. 3.23.1 it would be great.
>>
>>   Up to now, we've always kept the cmake version in sync with the value of
>> BR2_CMAKE_VERSION_MIN (defined in support/dependencies/check-host-cmake.mk and
>> updated every time there is a package that requires a specific newer version -
>> like swift would, as mentioned by Alsey.
>
> In addition to the Swift package mentioned by Alsey, there could be custom
> packages added by Buildroot users with external trees. This is what I am
> currently doing.
>
>>   What is the bug you were facing?
>
> Our custom package uses a feature which was buggy:
> https://gitlab.kitware.com/cmake/cmake/-/issues/18299 (it is also mentioned
> in the submitted patch). This bug was fixed in CMake 3.20.
>
>> Perhaps backporting its fix is appropriate?
>
> If the proposed patch with v.3.22 does not introduce any regression, then I
> personally do not see any reasons for backporting. 3.18 is two years old and
> it might be beneficial to switch to a newer one.

Backporting the cmake fix alone would not help hosts with cmake version
3.18 installed. With current BR2_CMAKE_VERSION_MIN set to 3.18 Buildroot
will not build the fixed cmake host package, but rely instead on the
buggy host installed cmake.

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-05-11 10:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 14:59 [Buildroot] [PATCH] package/cmake: bump version to 3.22.3 Andrey Nechypurenko
2022-03-29 18:25 ` Alsey Miller
2022-05-10 15:02 ` Andrey Nechypurenko
2022-05-10 15:05   ` Yegor Yefremov via buildroot
2022-05-10 15:20     ` Andrey Nechypurenko
2022-05-10 19:13       ` Arnout Vandecappelle
2022-05-11  9:45         ` Andrey Nechypurenko
2022-05-11 10:06           ` Baruch Siach via buildroot [this message]
2022-05-11 17:24             ` Arnout Vandecappelle
2022-05-11 17:58               ` Baruch Siach via buildroot
2022-05-12 22:07                 ` Arnout Vandecappelle
2022-05-19 16:18                   ` Andrey Nechypurenko
2022-05-24 12:03                     ` Andrey Nechypurenko
2022-05-12  9:12               ` Andrey Nechypurenko
2022-05-28 21:33 ` Yann E. MORIN
2022-05-30 12:38   ` Andrey Nechypurenko
2022-05-30 12:42     ` Andrey Nechypurenko
  -- strict thread matches above, loose matches on Subject: below --
2022-05-30 12:44 Andrey Nechypurenko
2022-05-30 12:57 ` Andrey Nechypurenko
2022-05-30 13:04   ` Baruch Siach via buildroot
2022-05-30 13:24     ` Andrey Nechypurenko

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=878rr88joi.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=alseycmiller@gmail.com \
    --cc=andreynech@gmail.com \
    --cc=baruch@tkos.co.il \
    --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