RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1816874 - Please provide a newer version of CMake (currently 3.17) in RHEL8
Summary: Please provide a newer version of CMake (currently 3.17) in RHEL8
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cmake
Version: 8.4
Hardware: All
OS: Linux
Target Milestone: rc
: 8.4
Assignee: serge_sans_paille
QA Contact: Michal Kolar
Eva-Lotte Gebhardt
: 1830748 1858941 1863276 (view as bug list)
Depends On: 1827927
Blocks: 1756974 1825061 1858983 1863276 1866550 1894575 1958316
TreeView+ depends on / blocked
Reported: 2020-03-24 23:12 UTC by Andrew Sanders
Modified: 2023-09-07 22:32 UTC (History)
13 users (show)

Fixed In Version: cmake-3.18.2-8.el8
Doc Type: Enhancement
Doc Text:
.CMake rebased to version 3.18.2 The CMake build system has been upgraded from version 3.11.4 to version 3.18.2. It is available in RHEL 8.4 as the `cmake-3.18.2-8.el8` package. To use CMake on a project that requires the version 3.18.2 or less, use the command `cmake_minimum_required(version x.y.z)`. For further information on new features and deprecated functionalities, see the link:https://cmake.org/cmake/help/latest/release[CMake Release Notes].
Clone Of:
Last Closed: 2021-05-18 15:16:28 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2021:1747 0 None None None 2021-05-18 15:16:45 UTC

Comment 21 Alexander Korsunsky 2020-08-21 14:35:48 UTC
As mentioned by Neal Gompa in Bug 1845910#c6, CMake 3.18 includes important CUDA-specific enhancements, such as support for using C++17 with CUDA.

I would kindly ask you to rebase to at least CMake 3.18 in the upcoming version.

Comment 26 Michal Kolar 2020-09-18 09:41:17 UTC
Tested against cmake-3.18.2-6.el8.

Comment 27 Tilmann Scheller 2020-09-21 09:26:33 UTC
*** Bug 1858941 has been marked as a duplicate of this bug. ***

Comment 28 serge_sans_paille 2020-09-22 10:10:20 UTC
New build: cmake-3.18.2-7.el8

Comment 29 Denis Arnaud 2020-09-22 11:32:12 UTC
From https://access.redhat.com/articles/rhel-eus, it seems that RHEL 8.4 would be released around mid-2021. Could anyone confirm this or point to more accurate release dates?

Comment 30 Tilmann Scheller 2020-09-22 13:08:18 UTC
Per https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates RHEL 8.0 was released on 2019-05-07. https://access.redhat.com/support/policy/updates/errata#RHEL8_Life_Cycle mentions "Minor releases are planned for release every six months through the Full Support phase.". RHEL 8 is currently in the Full Support phase. I.e. based on the above information RHEL 8.4 is likely to be released two years after RHEL 8.0 which would be around May 2021.
Disclaimer: Note that I'm purely quoting from publicly available Red Hat documentation here, this is not supposed to be interpreted as any kind of official public statement regarding the RHEL 8.4 release date by any means.

Comment 31 Denis Arnaud 2020-09-22 13:42:17 UTC
(In reply to Tilmann Scheller from comment #30)
> [...] based on the above information RHEL 8.4 is likely to be released two
> years after RHEL 8.0 which would be around May 2021.


Comment 35 Michal Kolar 2020-09-25 09:59:50 UTC
Verified against cmake-3.18.2-7.el8

Comment 37 Tilmann Scheller 2020-10-28 10:41:38 UTC
*** Bug 1863276 has been marked as a duplicate of this bug. ***

Comment 38 Tilmann Scheller 2020-10-28 10:52:39 UTC
*** Bug 1830748 has been marked as a duplicate of this bug. ***

Comment 39 serge_sans_paille 2020-10-28 16:51:20 UTC
Just rebuilt cmake-3.18.2-8.el8 linking with system libarchive instead of bundling it.

Comment 44 Michal Kolar 2020-11-10 11:42:30 UTC
Verified against cmake-3.18.2-8.el8.

Comment 45 Richard Shaw 2020-11-30 15:23:22 UTC
When will the newer version of CMake be available for actual use (specifically in EPEL)?

Comment 46 Tilmann Scheller 2020-12-18 15:21:31 UTC
Richard, this bug only tracks the CMake rebase in RHEL 8.4, I'm not sure what the EPEL situation/plan is. Please also see https://bugzilla.redhat.com/show_bug.cgi?id=1816874#c30 for some information on when this is expected to ship.

Comment 47 Carl George 🤠 2020-12-23 18:19:43 UTC
Richard, EPEL builds against RHEL, so shortly after RHEL 8.4 is released it will be synced to the EPEL 8 buildroot.

If you want to start testing the new cmake package now, it's available in CentOS Stream 8.

[root@cs8-container:~]# repoquery -q cmake

Comment 55 errata-xmlrpc 2021-05-18 15:16:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (cmake bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.