All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Nechypurenko <andreynech@gmail.com>
To: buildroot@buildroot.org
Cc: Andrey Nechypurenko <andreynech@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH] package/cmake: bump version to 3.22.3
Date: Mon, 30 May 2022 14:44:49 +0200	[thread overview]
Message-ID: <20220530124450.19073-1-andreynech@gmail.com> (raw)

Version 3.20 is the first one where the following issue is fixed:
https://gitlab.kitware.com/cmake/cmake/-/issues/18299
Was affected by this bug and decide to bump the version to the
latest stable
---
 package/cmake/cmake.hash | 4 ++--
 package/cmake/cmake.mk   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/package/cmake/cmake.hash b/package/cmake/cmake.hash
index da514a6d6b..1749db8c27 100644
--- a/package/cmake/cmake.hash
+++ b/package/cmake/cmake.hash
@@ -1,5 +1,5 @@
-# From https://cmake.org/files/v3.18/cmake-3.18.6-SHA-256.txt
-sha256  124f571ab70332da97a173cb794dfa09a5b20ccbb80a08e56570a500f47b6600  cmake-3.18.6.tar.gz
+# From https://cmake.org/files/v3.22/cmake-3.22.3-SHA-256.txt
+sha256  9f8469166f94553b6978a16ee29227ec49a2eb5ceb608275dec40d8ae0d1b5a0  cmake-3.22.3.tar.gz
 
 # Locally calculated
 sha256  131b9ff756b64a25b7461c3c1382e70b16c70a5b4833a1577897fa3ea6d88f8d  Copyright.txt
diff --git a/package/cmake/cmake.mk b/package/cmake/cmake.mk
index 4177b119ab..053658fad6 100644
--- a/package/cmake/cmake.mk
+++ b/package/cmake/cmake.mk
@@ -4,8 +4,8 @@
 #
 ################################################################################
 
-CMAKE_VERSION_MAJOR = 3.18
-CMAKE_VERSION = $(CMAKE_VERSION_MAJOR).6
+CMAKE_VERSION_MAJOR = 3.22
+CMAKE_VERSION = $(CMAKE_VERSION_MAJOR).3
 CMAKE_SITE = https://cmake.org/files/v$(CMAKE_VERSION_MAJOR)
 CMAKE_LICENSE = BSD-3-Clause
 CMAKE_LICENSE_FILES = Copyright.txt
-- 
2.32.0

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

             reply	other threads:[~2022-05-30 12:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 12:44 Andrey Nechypurenko [this message]
2022-05-30 12:57 ` [Buildroot] [PATCH] package/cmake: bump version to 3.22.3 Andrey Nechypurenko
2022-05-30 13:04   ` Baruch Siach via buildroot
2022-05-30 13:24     ` Andrey Nechypurenko
  -- strict thread matches above, loose matches on Subject: below --
2022-03-29 14:59 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
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

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=20220530124450.19073-1-andreynech@gmail.com \
    --to=andreynech@gmail.com \
    --cc=buildroot@buildroot.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.