| Message ID | 20250703132720.3378569-1-Moritz.Haase@bmw.de |
|---|---|
| Headers | show |
| Series | cmake: Major version bump to 4.0.3 | expand |
Moritz While this change is a good one, this does have some implications on the recipes especially from meta-openembedded, there are almost 100 which are failing, perhaps some of them are easy and others are not to fix, but this does look invasive in nature. Like oe-core has been fixed, I am afraid we need to fix meta-openembedded layers too. Here is a sample world build logs for qemuarm https://errors.yoctoproject.org/Errors/Build/210889/?page=1 This is also a call for recipe maintainers to fix the concerned recipes if they are impacted. On Thu, Jul 3, 2025 at 6:27 AM Moritz Haase via lists.openembedded.org <Moritz.Haase=bmw.de@lists.openembedded.org> wrote: > > This patch series bumps CMake to 4.0.3, the most current of the 4.x releases. > That bump allows us to drop all of the upstreamable patches for CMake itself > that we currently carry, which was the motivation for the update as suggested by > Alex Kanavin in [0]. > > A number of components require (minor) patches to build with the new CMake > version. In most cases, those are backports of commits that haven't made it into > an upstream release yet. > > The bump depends on this patches, but not vice-versa (since we are already on > CMake 3.31). Thus, if desired, it would be possible to pull the 'Allow builds > with CMake 4+' patches in in advance of the actual bump. > > changes in v5: > - Fix for oe_selftest failure in 'DevtoolAddTests.test_devtool_add_library' > - Updated patch for musl-locales based on upstream feedback > > changes in v4: > - Fixed broken patch formatting. > > changes in v3: > > - Updated patch series description. > - Added four additional commits with patches for build failures seen on > Autobuilder. Those should be all be fixed now, apart from the one in > meta-virt (yajl-2.1.0), which I don't have set up locally. > - Fix for test failure seen in SDK tests. > > changes in v2: > > - Re-ordered / squashed commits to keep bisectability (see [3], [4]) > - Fixed patchtest findings > > [0]: https://lists.openembedded.org/g/openembedded-core/message/219113 > [1]: https://git.openembedded.org/openembedded-core/commit/?id=c3efca7495889f3682225af8c9e01ceb094b1bb7 > [2]: https://git.openembedded.org/openembedded-core/commit/?id=cb5234acdab200bd43b89416d8d7e9df91af58cc > [3]: https://lists.openembedded.org/g/openembedded-core/message/219403 > [4]: https://lists.openembedded.org/g/openembedded-core/message/219425 > > CC: alex.kanavin@gmail.com > CC: quentin.schulz@cherry.de > CC: antonin.godard@bootlin.com > CC: Peter.Marko@siemens.com > > Moritz Haase (7): > libcomps: Backport patch to support builds with CMake 4+ > createrepo-c: Backport patches to support builds with CMake 4+ > apt: Backport patch to support builds with CMake 4+ > libubootenv: Backport patch to support builds with CMake 4+ > musl-locales: Add patch to support builds with CMake 4+ > libwpe: Add patch to support builds with CMake 4+ > cmake: upgrade 3.31.6 -> 4.0.3 > > .../sdkext/files/myapp_cmake/CMakeLists.txt | 2 +- > meta/lib/oeqa/selftest/cases/devtool.py | 10 +- > ...Update-cmake_minimum_required-to-3.5.patch | 50 ++++ > meta/recipes-bsp/u-boot/libubootenv_0.3.6.bb | 4 +- > ...red-CMake-version-to-3.5-to-allow-bu.patch | 41 ++++ > meta/recipes-core/musl/musl-locales_git.bb | 4 +- > ...mum_required-to-3.13-to-avoid-warnin.patch | 47 ++++ > meta/recipes-devtools/apt/apt_2.6.1.bb | 1 + > ...native_3.31.6.bb => cmake-native_4.0.3.bb} | 6 +- > meta/recipes-devtools/cmake/cmake.inc | 8 +- > ...mpilerABI-Strip-pipe-from-compile-fl.patch | 63 ----- > ...xt2fs-ext2_fs.h-by-cmake-s-internal.patch} | 4 +- > ...ng-undocumented-type-for-CURLOPT_NET.patch | 30 --- > ...trary-characters-in-test-names-of-CT.patch | 202 ---------------- > ...-CMakeLists.txt-disable-USE_NGHTTP2.patch} | 6 +- > .../cmake/{cmake_3.31.6.bb => cmake_4.0.3.bb} | 1 - > .../0001-Fix-libname-of-Libs.private.patch | 22 ++ > ...ED_TARGET-for-3rd-party-dependencies.patch | 226 ++++++++++++++++++ > ...-imported-targets-of-turned-off-depe.patch | 53 ++++ > ...ds-without-Doxygen-being-present-wit.patch | 50 ++++ > .../createrepo-c/createrepo-c_1.2.1.bb | 4 + > ...libcomps-Support-builds-with-CMake-4.patch | 132 ++++++++++ > .../libcomps/libcomps_0.1.21.bb | 1 + > ...red-CMake-version-to-3.5-to-allow-bu.patch | 38 +++ > meta/recipes-sato/webkit/libwpe_1.16.2.bb | 6 +- > 25 files changed, 695 insertions(+), 316 deletions(-) > create mode 100644 meta/recipes-bsp/u-boot/libubootenv/0001-Update-cmake_minimum_required-to-3.5.patch > create mode 100644 meta/recipes-core/musl/musl-locales/0001-cmake-Bump-required-CMake-version-to-3.5-to-allow-bu.patch > create mode 100644 meta/recipes-devtools/apt/apt/0001-Raise-cmake_minimum_required-to-3.13-to-avoid-warnin.patch > rename meta/recipes-devtools/cmake/{cmake-native_3.31.6.bb => cmake-native_4.0.3.bb} (90%) > delete mode 100644 meta/recipes-devtools/cmake/cmake/0001-CMakeDetermineCompilerABI-Strip-pipe-from-compile-fl.patch > rename meta/recipes-devtools/cmake/cmake/{0005-Disable-use-of-ext2fs-ext2_fs.h-by-cmake-s-internal-.patch => 0001-Disable-use-of-ext2fs-ext2_fs.h-by-cmake-s-internal.patch} (90%) > delete mode 100644 meta/recipes-devtools/cmake/cmake/0001-cmCurl-Avoid-using-undocumented-type-for-CURLOPT_NET.patch > delete mode 100644 meta/recipes-devtools/cmake/cmake/0001-ctest-Allow-arbitrary-characters-in-test-names-of-CT.patch > rename meta/recipes-devtools/cmake/cmake/{0001-CMakeLists.txt-disable-USE_NGHTTP2.patch => 0002-CMakeLists.txt-disable-USE_NGHTTP2.patch} (83%) > rename meta/recipes-devtools/cmake/{cmake_3.31.6.bb => cmake_4.0.3.bb} (96%) > create mode 100644 meta/recipes-devtools/createrepo-c/createrepo-c/0001-Fix-libname-of-Libs.private.patch > create mode 100644 meta/recipes-devtools/createrepo-c/createrepo-c/0002-Use-IMPORTED_TARGET-for-3rd-party-dependencies.patch > create mode 100644 meta/recipes-devtools/createrepo-c/createrepo-c/0003-Don-t-try-to-use-imported-targets-of-turned-off-depe.patch > create mode 100644 meta/recipes-devtools/createrepo-c/createrepo-c/0004-cmake-Allow-builds-without-Doxygen-being-present-wit.patch > create mode 100644 meta/recipes-devtools/libcomps/libcomps/0001-libcomps-Support-builds-with-CMake-4.patch > create mode 100644 meta/recipes-sato/webkit/libwpe/0001-cmake-Bump-required-CMake-version-to-3.5-to-allow-bu.patch > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#219881): https://lists.openembedded.org/g/openembedded-core/message/219881 > Mute This Topic: https://lists.openembedded.org/mt/113965735/1997914 > Group Owner: openembedded-core+owner@lists.openembedded.org > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [raj.khem@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- >
Hi everyone, I have started fixing recipes in meta-openembedded, but I'm not sure how we can prevent multiple people from working on the same recipe at the same time. Since it's likely that others will also start fixing recipes, maybe we need a way to coordinate or reserve recipes to avoid duplicate efforts. Otherwise, there’s a chance that two people could start fixing the same recipe without knowing about each other’s work. Is there any recommended way to coordinate, or maybe we could create a list or use issues to "claim" a recipe before starting to work on it?
Hi, > While this change is a good one, this does have some implications on > the recipes especially from meta-openembedded, there are almost 100 > which are failing, perhaps some of them are easy and others are not to > fix, but this does look invasive in nature. Like oe-core has been >fixed, I am afraid we need to fix meta-openembedded layers too. Here > is a sample world build logs for qemuarm > > https://errors.yoctoproject.org/Errors/Build/210889/?page=1 I'm happy to support here. I'd agree to what Alper said though: Some way of coordinating this effort seems to be required. Given the number of affected recipes it'd also be good to have a temporary branch / fork to prepare the patches on. Are there some pointers we can follow from previous changes of the same kind? One idea I had to possibly speed the process up a bit: For starters, we could try building the "broken" recipes with -DCMAKE_POLICY_VERSION_MINIMUM=3.5 added to EXTRA_OECMAKE possibly via a temporary 'cmake-4-enforce-policy-compat' bbclass or some similar mechanism. That would be faster then checking upstream for CMake-related patches and adding them to the tree / recipes. Moritz
On Mon, Jul 7, 2025 at 10:45 PM Haase Moritz, JD-62 <Moritz.Haase@bmw.de> wrote: > > Hi, > > > While this change is a good one, this does have some implications on > > the recipes especially from meta-openembedded, there are almost 100 > > which are failing, perhaps some of them are easy and others are not to > > fix, but this does look invasive in nature. Like oe-core has been > >fixed, I am afraid we need to fix meta-openembedded layers too. Here > > is a sample world build logs for qemuarm > > > > https://errors.yoctoproject.org/Errors/Build/210889/?page=1 > > I'm happy to support here. I'd agree to what Alper said though: Some way of > coordinating this effort seems to be required. Given the number of affected > recipes it'd also be good to have a temporary branch / fork to prepare the > patches on. Are there some pointers we can follow from previous changes > of the same kind? I am collecting the fixed into master-next staging branch already. > > One idea I had to possibly speed the process up a bit: For starters, we could > try building the "broken" recipes with > > -DCMAKE_POLICY_VERSION_MINIMUM=3.5 > > added to > > EXTRA_OECMAKE > > possibly via a temporary 'cmake-4-enforce-policy-compat' bbclass or some similar > mechanism. That would be faster then checking upstream for CMake-related patches > and adding them to the tree / recipes. > > Moritz > >
> > I'm happy to support here. I'd agree to what Alper said though: Some way > of > coordinating this effort seems to be required. Given the number of > affected > recipes it'd also be good to have a temporary branch / fork to prepare the > > patches on. Are there some pointers we can follow from previous changes > of the same kind? > > > One idea I had to possibly speed the process up a bit: For starters, we > could > try building the "broken" recipes with > > > -DCMAKE_POLICY_VERSION_MINIMUM=3.5 > > > added to > > > EXTRA_OECMAKE > > > possibly via a temporary 'cmake-4-enforce-policy-compat' bbclass or some > similar > mechanism. That would be faster then checking upstream for CMake-related > patches > and adding them to the tree / recipes. > I also considered the idea of temporarily using -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to quickly work around the CMake 4 issues across multiple recipes. Then, I thought that directly upgrading recipes where the upstream version could be updated was more sustainable solution. I believed this would resolve many compatibility issues by relying on upstream fixes and encourage the community to use the latest versions. However, in cases where upgrading is not possible or incompatibilities persist, adding a small patch (for example, allow-build-with-cmake-4.patch) that sets the minimum required CMake version to 3.5 can provide a sustainable workaround. On the other hand, applying similar patches across many recipes may require manual cleanup in the future if the issue is eventually resolved upstream. Therefore, it is essential to keep track of synchronization with upstream over the long term. Before our conversation I made a few things and sent them to meta-openembedded and Khem accepted them to master-next, but I still had the feeling that maybe something better could be done. https://patchwork.yoctoproject.org/project/oe/list/?submitter=938 As I said, I have the feeling that it can be done better, so I will wait for your answers before I do anything.
Hi, > I also considered the idea of temporarily using > -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to quickly work around the CMake 4 issues > across multiple recipes. Then, I thought that directly upgrading recipes where > the upstream version could be updated was more sustainable solution. I > believed this would resolve many compatibility issues by relying on upstream > fixes and encourage the community to use the latest versions. > > [...] I totally agree. Updating should be the preferred approach, followed by patching and the policy workaround. > Before our conversation I made a few things and sent them to meta-openembedded > and Khem accepted them to master-next, but I still had the feeling that maybe > something better could be done. Awesome, thanks! > As I said, I have the feeling that it can be done better, so I will wait for > your answers before I do anything. How about splitting the remaining build failures in half (after sorting them alphabetically by recipe name?). Would start working on the *second* half then. In case of dependency issues we can sync here. @Khem: Would you mind sharing a link to the failures of the latest 'master-next' build? Moritz
On Wed, Jul 9, 2025 at 11:34 PM Haase Moritz, JD-62 <Moritz.Haase@bmw.de> wrote: > > Hi, > > > I also considered the idea of temporarily using > > -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to quickly work around the CMake 4 issues > > across multiple recipes. Then, I thought that directly upgrading recipes where > > the upstream version could be updated was more sustainable solution. I > > believed this would resolve many compatibility issues by relying on upstream > > fixes and encourage the community to use the latest versions. > > > > [...] > > I totally agree. Updating should be the preferred approach, followed by patching > and the policy workaround. > > > Before our conversation I made a few things and sent them to meta-openembedded > > and Khem accepted them to master-next, but I still had the feeling that maybe > > something better could be done. > > Awesome, thanks! > > > As I said, I have the feeling that it can be done better, so I will wait for > > your answers before I do anything. > > How about splitting the remaining build failures in half (after sorting them > alphabetically by recipe name?). Would start working on the *second* half then. > In case of dependency issues we can sync here. > > @Khem: Would you mind sharing a link to the failures of the latest 'master-next' > build? > Alper has sent a set of fixes which lowered the volume quite a bit, Thanks a lot Alper !. it's down to 52 now. here is latest qemuarm run https://errors.yoctoproject.org/Errors/Build/211141/?limit=100 > Moritz >
Hello everyone, It looks like Markus is also sending fixes to meta-openembedded regarding the CMake 4+ compatibility issue, so I have added him to cc as well. I collected the errors from Khem’s latest qemuarm run into a spreadsheet and added checkboxes. You can tick off the ones you have fixed, so we can avoid conflicts and waste of time. https://docs.google.com/spreadsheets/d/1X8LN9x4xhqqzuAiTdE27pJdabS1P9ijeuUGAL6oQyzo/edit?usp=sharing Khem Raj <raj.khem@gmail.com>, 10 Tem 2025 Per, 20:40 tarihinde şunu yazdı: > > On Wed, Jul 9, 2025 at 11:34 PM Haase Moritz, JD-62 <Moritz.Haase@bmw.de> wrote: > > > > Hi, > > > > > I also considered the idea of temporarily using > > > -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to quickly work around the CMake 4 issues > > > across multiple recipes. Then, I thought that directly upgrading recipes where > > > the upstream version could be updated was more sustainable solution. I > > > believed this would resolve many compatibility issues by relying on upstream > > > fixes and encourage the community to use the latest versions. > > > > > > [...] > > > > I totally agree. Updating should be the preferred approach, followed by patching > > and the policy workaround. > > > > > Before our conversation I made a few things and sent them to meta-openembedded > > > and Khem accepted them to master-next, but I still had the feeling that maybe > > > something better could be done. > > > > Awesome, thanks! > > > > > As I said, I have the feeling that it can be done better, so I will wait for > > > your answers before I do anything. > > > > How about splitting the remaining build failures in half (after sorting them > > alphabetically by recipe name?). Would start working on the *second* half then. > > In case of dependency issues we can sync here. > > > > @Khem: Would you mind sharing a link to the failures of the latest 'master-next' > > build? > > > > Alper has sent a set of fixes which lowered the volume quite a bit, > Thanks a lot Alper !. it's down to 52 now. > here is latest qemuarm run > > https://errors.yoctoproject.org/Errors/Build/211141/?limit=100 > > > > Moritz > >
41 more to go - https://errors.yoctoproject.org/Errors/Build/211165/?limit=50 On Thu, Jul 10, 2025 at 12:10 PM Alper Ak <alperyasinak1@gmail.com> wrote: > > Hello everyone, > > It looks like Markus is also sending fixes to meta-openembedded > regarding the CMake 4+ compatibility issue, so I have added him to cc > as well. > > I collected the errors from Khem’s latest qemuarm run into a > spreadsheet and added checkboxes. You can tick off the ones you have > fixed, so we can avoid conflicts and waste of time. > > https://docs.google.com/spreadsheets/d/1X8LN9x4xhqqzuAiTdE27pJdabS1P9ijeuUGAL6oQyzo/edit?usp=sharing > > Khem Raj <raj.khem@gmail.com>, 10 Tem 2025 Per, 20:40 tarihinde şunu yazdı: > > > > On Wed, Jul 9, 2025 at 11:34 PM Haase Moritz, JD-62 <Moritz.Haase@bmw.de> wrote: > > > > > > Hi, > > > > > > > I also considered the idea of temporarily using > > > > -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to quickly work around the CMake 4 issues > > > > across multiple recipes. Then, I thought that directly upgrading recipes where > > > > the upstream version could be updated was more sustainable solution. I > > > > believed this would resolve many compatibility issues by relying on upstream > > > > fixes and encourage the community to use the latest versions. > > > > > > > > [...] > > > > > > I totally agree. Updating should be the preferred approach, followed by patching > > > and the policy workaround. > > > > > > > Before our conversation I made a few things and sent them to meta-openembedded > > > > and Khem accepted them to master-next, but I still had the feeling that maybe > > > > something better could be done. > > > > > > Awesome, thanks! > > > > > > > As I said, I have the feeling that it can be done better, so I will wait for > > > > your answers before I do anything. > > > > > > How about splitting the remaining build failures in half (after sorting them > > > alphabetically by recipe name?). Would start working on the *second* half then. > > > In case of dependency issues we can sync here. > > > > > > @Khem: Would you mind sharing a link to the failures of the latest 'master-next' > > > build? > > > > > > > Alper has sent a set of fixes which lowered the volume quite a bit, > > Thanks a lot Alper !. it's down to 52 now. > > here is latest qemuarm run > > > > https://errors.yoctoproject.org/Errors/Build/211141/?limit=100 > > > > > > > Moritz > > >
Hi, awesome, we are closing the gap :) I just sent another 10 patches to the mailing list via [0]. Hope to get some more done today, will keep the shared spreadsheet (very good idea BTW) updated. [0]: https://lists.openembedded.org/g/openembedded-devel/topic/meta_oe_patch_00_10/114097827 Moritz
Somehow errors.yp.org is not responsing so my latest build errors are not being reported, we are left with 28 failures Summary: 26 tasks failed: meta-openembedded/meta-oe/recipes-dbs/leveldb/leveldb_1.23.bb:do_configure meta-openembedded/meta-oe/recipes-connectivity/obex/openobex_1.7.2.bb:do_configure meta-openembedded/meta-oe/recipes-navigation/proj/proj_9.3.1.bb:do_configure meta-openembedded/meta-oe/recipes-graphics/libvncserver/libvncserver_0.9.14.bb:do_configure meta-openembedded/meta-oe/recipes-extended/wxwidgets/wxwidgets_3.2.6.bb:do_configure meta-openembedded/meta-oe/recipes-devtools/libubox/libubox_git.bb:do_configure meta-openembedded/meta-oe/recipes-support/freerdp/freerdp_2.11.7.bb:do_configure meta-openembedded/meta-oe/recipes-dbs/soci/soci_4.0.3.bb:do_configure meta-openembedded/meta-multimedia/recipes-dvb/oscam/oscam_1.20.bb:do_configure meta-openembedded/meta-xfce/recipes-panel-plugins/whiskermenu/xfce4-whiskermenu-plugin_2.7.1.bb:do_configure meta-openembedded/meta-multimedia/recipes-multimedia/musicbrainz/libmusicbrainz_git.bb:do_compile virtual:native:meta-openembedded/meta-oe/recipes-connectivity/obex/openobex_1.7.2.bb:do_configure meta-openembedded/meta-xfce/recipes-apps/catfish/catfish_4.18.0.bb:do_configure virtual:native:meta-openembedded/meta-oe/recipes-navigation/proj/proj_9.3.1.bb:do_configure meta-openembedded/meta-networking/recipes-connectivity/civetweb/civetweb_1.16.bb:do_configure meta-openembedded/meta-oe/recipes-connectivity/zeromq/czmq_4.2.1.bb:do_configure virtual:native:meta-openembedded/meta-oe/recipes-extended/wxwidgets/wxwidgets_3.2.6.bb:do_configure meta-openembedded/meta-oe/recipes-extended/minifi-cpp/minifi-cpp_0.99.1.bb:do_configure meta-openembedded/meta-oe/recipes-extended/openwsman/openwsman_2.7.2.bb:do_configure meta-openembedded/meta-networking/recipes-connectivity/openthread/ot-br-posix_git.bb:do_configure meta-openembedded/meta-networking/recipes-connectivity/openthread/ot-daemon_git.bb:do_configure meta-openembedded/meta-oe/recipes-graphics/vk-gl-cts/opengl-es-cts_3.2.12.0.bb:do_configure meta-openembedded/meta-networking/recipes-connectivity/nanomsg/nngpp_git.bb:do_configure meta-openembedded/meta-oe/recipes-connectivity/gattlib/gattlib_git.bb:do_configure meta-openembedded/meta-oe/recipes-connectivity/transmission/transmission_4.0.6.bb:do_compile meta-openembedded/meta-oe/recipes-support/opencv/opencv_4.11.0.bb:do_compile On Fri, Jul 11, 2025 at 3:25 AM Haase Moritz, JD-62 <Moritz.Haase@bmw.de> wrote: > > Hi, > > awesome, we are closing the gap :) I just sent another 10 patches to the mailing > list via [0]. Hope to get some more done today, will keep the shared spreadsheet > (very good idea BTW) updated. > > [0]: https://lists.openembedded.org/g/openembedded-devel/topic/meta_oe_patch_00_10/114097827 > > Moritz
We are left with 16 recipes to fix, here are latest qemuarm world build results https://errors.yoctoproject.org/Errors/Build/211210/ On Sat, Jul 12, 2025 at 9:22 AM Khem Raj <raj.khem@gmail.com> wrote: > > Somehow errors.yp.org is not responsing so my latest build errors are > not being reported, we are left with 28 failures > > Summary: 26 tasks failed: > meta-openembedded/meta-oe/recipes-dbs/leveldb/leveldb_1.23.bb:do_configure > meta-openembedded/meta-oe/recipes-connectivity/obex/openobex_1.7.2.bb:do_configure > meta-openembedded/meta-oe/recipes-navigation/proj/proj_9.3.1.bb:do_configure > meta-openembedded/meta-oe/recipes-graphics/libvncserver/libvncserver_0.9.14.bb:do_configure > meta-openembedded/meta-oe/recipes-extended/wxwidgets/wxwidgets_3.2.6.bb:do_configure > meta-openembedded/meta-oe/recipes-devtools/libubox/libubox_git.bb:do_configure > meta-openembedded/meta-oe/recipes-support/freerdp/freerdp_2.11.7.bb:do_configure > meta-openembedded/meta-oe/recipes-dbs/soci/soci_4.0.3.bb:do_configure > meta-openembedded/meta-multimedia/recipes-dvb/oscam/oscam_1.20.bb:do_configure > meta-openembedded/meta-xfce/recipes-panel-plugins/whiskermenu/xfce4-whiskermenu-plugin_2.7.1.bb:do_configure > meta-openembedded/meta-multimedia/recipes-multimedia/musicbrainz/libmusicbrainz_git.bb:do_compile > virtual:native:meta-openembedded/meta-oe/recipes-connectivity/obex/openobex_1.7.2.bb:do_configure > meta-openembedded/meta-xfce/recipes-apps/catfish/catfish_4.18.0.bb:do_configure > virtual:native:meta-openembedded/meta-oe/recipes-navigation/proj/proj_9.3.1.bb:do_configure > meta-openembedded/meta-networking/recipes-connectivity/civetweb/civetweb_1.16.bb:do_configure > meta-openembedded/meta-oe/recipes-connectivity/zeromq/czmq_4.2.1.bb:do_configure > virtual:native:meta-openembedded/meta-oe/recipes-extended/wxwidgets/wxwidgets_3.2.6.bb:do_configure > meta-openembedded/meta-oe/recipes-extended/minifi-cpp/minifi-cpp_0.99.1.bb:do_configure > meta-openembedded/meta-oe/recipes-extended/openwsman/openwsman_2.7.2.bb:do_configure > meta-openembedded/meta-networking/recipes-connectivity/openthread/ot-br-posix_git.bb:do_configure > meta-openembedded/meta-networking/recipes-connectivity/openthread/ot-daemon_git.bb:do_configure > meta-openembedded/meta-oe/recipes-graphics/vk-gl-cts/opengl-es-cts_3.2.12.0.bb:do_configure > meta-openembedded/meta-networking/recipes-connectivity/nanomsg/nngpp_git.bb:do_configure > meta-openembedded/meta-oe/recipes-connectivity/gattlib/gattlib_git.bb:do_configure > meta-openembedded/meta-oe/recipes-connectivity/transmission/transmission_4.0.6.bb:do_compile > meta-openembedded/meta-oe/recipes-support/opencv/opencv_4.11.0.bb:do_compile > > On Fri, Jul 11, 2025 at 3:25 AM Haase Moritz, JD-62 <Moritz.Haase@bmw.de> wrote: > > > > Hi, > > > > awesome, we are closing the gap :) I just sent another 10 patches to the mailing > > list via [0]. Hope to get some more done today, will keep the shared spreadsheet > > (very good idea BTW) updated. > > > > [0]: https://lists.openembedded.org/g/openembedded-devel/topic/meta_oe_patch_00_10/114097827 > > > > Moritz
12 left https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/2959398/raw_inline On Sat, Jul 12, 2025 at 10:45 PM Khem Raj <raj.khem@gmail.com> wrote: > > We are left with 16 recipes to fix, here are latest qemuarm world build results > > https://errors.yoctoproject.org/Errors/Build/211210/ > > > On Sat, Jul 12, 2025 at 9:22 AM Khem Raj <raj.khem@gmail.com> wrote: > > > > Somehow errors.yp.org is not responsing so my latest build errors are > > not being reported, we are left with 28 failures > > > > Summary: 26 tasks failed: > > meta-openembedded/meta-oe/recipes-dbs/leveldb/leveldb_1.23.bb:do_configure > > meta-openembedded/meta-oe/recipes-connectivity/obex/openobex_1.7.2.bb:do_configure > > meta-openembedded/meta-oe/recipes-navigation/proj/proj_9.3.1.bb:do_configure > > meta-openembedded/meta-oe/recipes-graphics/libvncserver/libvncserver_0.9.14.bb:do_configure > > meta-openembedded/meta-oe/recipes-extended/wxwidgets/wxwidgets_3.2.6.bb:do_configure > > meta-openembedded/meta-oe/recipes-devtools/libubox/libubox_git.bb:do_configure > > meta-openembedded/meta-oe/recipes-support/freerdp/freerdp_2.11.7.bb:do_configure > > meta-openembedded/meta-oe/recipes-dbs/soci/soci_4.0.3.bb:do_configure > > meta-openembedded/meta-multimedia/recipes-dvb/oscam/oscam_1.20.bb:do_configure > > meta-openembedded/meta-xfce/recipes-panel-plugins/whiskermenu/xfce4-whiskermenu-plugin_2.7.1.bb:do_configure > > meta-openembedded/meta-multimedia/recipes-multimedia/musicbrainz/libmusicbrainz_git.bb:do_compile > > virtual:native:meta-openembedded/meta-oe/recipes-connectivity/obex/openobex_1.7.2.bb:do_configure > > meta-openembedded/meta-xfce/recipes-apps/catfish/catfish_4.18.0.bb:do_configure > > virtual:native:meta-openembedded/meta-oe/recipes-navigation/proj/proj_9.3.1.bb:do_configure > > meta-openembedded/meta-networking/recipes-connectivity/civetweb/civetweb_1.16.bb:do_configure > > meta-openembedded/meta-oe/recipes-connectivity/zeromq/czmq_4.2.1.bb:do_configure > > virtual:native:meta-openembedded/meta-oe/recipes-extended/wxwidgets/wxwidgets_3.2.6.bb:do_configure > > meta-openembedded/meta-oe/recipes-extended/minifi-cpp/minifi-cpp_0.99.1.bb:do_configure > > meta-openembedded/meta-oe/recipes-extended/openwsman/openwsman_2.7.2.bb:do_configure > > meta-openembedded/meta-networking/recipes-connectivity/openthread/ot-br-posix_git.bb:do_configure > > meta-openembedded/meta-networking/recipes-connectivity/openthread/ot-daemon_git.bb:do_configure > > meta-openembedded/meta-oe/recipes-graphics/vk-gl-cts/opengl-es-cts_3.2.12.0.bb:do_configure > > meta-openembedded/meta-networking/recipes-connectivity/nanomsg/nngpp_git.bb:do_configure > > meta-openembedded/meta-oe/recipes-connectivity/gattlib/gattlib_git.bb:do_configure > > meta-openembedded/meta-oe/recipes-connectivity/transmission/transmission_4.0.6.bb:do_compile > > meta-openembedded/meta-oe/recipes-support/opencv/opencv_4.11.0.bb:do_compile > > > > On Fri, Jul 11, 2025 at 3:25 AM Haase Moritz, JD-62 <Moritz.Haase@bmw.de> wrote: > > > > > > Hi, > > > > > > awesome, we are closing the gap :) I just sent another 10 patches to the mailing > > > list via [0]. Hope to get some more done today, will keep the shared spreadsheet > > > (very good idea BTW) updated. > > > > > > [0]: https://lists.openembedded.org/g/openembedded-devel/topic/meta_oe_patch_00_10/114097827 > > > > > > Moritz
Hi, I sent another 11 patches. So hopefully the only one missing is openwsman, which I can't build locally. For sysdig, I tried to update to the latest release (0.40.1), but couldn't get the build to pass due to many new dependencies, so I opted for the policy override. If anybody is interested in trying to finish the update, I can share what I have. Moritz
On Mon, Jul 14, 2025 at 5:16 AM Moritz Haase via lists.openembedded.org <Moritz.Haase=bmw.de@lists.openembedded.org> wrote: > > Hi, > > I sent another 11 patches. So hopefully the only one missing is > openwsman, which > I can't build locally. > > For sysdig, I tried to update to the latest release (0.40.1), but > couldn't get > the build to pass due to many new dependencies, so I opted for the policy > override. If anybody is interested in trying to finish the update, I can > share > what I have. Thanks, this makes the list down to 3 https://errors.yoctoproject.org/Errors/Build/211282/ > > Moritz > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#220227): https://lists.openembedded.org/g/openembedded-core/message/220227 > Mute This Topic: https://lists.openembedded.org/mt/113965735/1997914 > Group Owner: openembedded-core+owner@lists.openembedded.org > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [raj.khem@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- >
This patch series bumps CMake to 4.0.3, the most current of the 4.x releases. That bump allows us to drop all of the upstreamable patches for CMake itself that we currently carry, which was the motivation for the update as suggested by Alex Kanavin in [0]. A number of components require (minor) patches to build with the new CMake version. In most cases, those are backports of commits that haven't made it into an upstream release yet. The bump depends on this patches, but not vice-versa (since we are already on CMake 3.31). Thus, if desired, it would be possible to pull the 'Allow builds with CMake 4+' patches in in advance of the actual bump. changes in v5: - Fix for oe_selftest failure in 'DevtoolAddTests.test_devtool_add_library' - Updated patch for musl-locales based on upstream feedback changes in v4: - Fixed broken patch formatting. changes in v3: - Updated patch series description. - Added four additional commits with patches for build failures seen on Autobuilder. Those should be all be fixed now, apart from the one in meta-virt (yajl-2.1.0), which I don't have set up locally. - Fix for test failure seen in SDK tests. changes in v2: - Re-ordered / squashed commits to keep bisectability (see [3], [4]) - Fixed patchtest findings [0]: https://lists.openembedded.org/g/openembedded-core/message/219113 [1]: https://git.openembedded.org/openembedded-core/commit/?id=c3efca7495889f3682225af8c9e01ceb094b1bb7 [2]: https://git.openembedded.org/openembedded-core/commit/?id=cb5234acdab200bd43b89416d8d7e9df91af58cc [3]: https://lists.openembedded.org/g/openembedded-core/message/219403 [4]: https://lists.openembedded.org/g/openembedded-core/message/219425 CC: alex.kanavin@gmail.com CC: quentin.schulz@cherry.de CC: antonin.godard@bootlin.com CC: Peter.Marko@siemens.com Moritz Haase (7): libcomps: Backport patch to support builds with CMake 4+ createrepo-c: Backport patches to support builds with CMake 4+ apt: Backport patch to support builds with CMake 4+ libubootenv: Backport patch to support builds with CMake 4+ musl-locales: Add patch to support builds with CMake 4+ libwpe: Add patch to support builds with CMake 4+ cmake: upgrade 3.31.6 -> 4.0.3 .../sdkext/files/myapp_cmake/CMakeLists.txt | 2 +- meta/lib/oeqa/selftest/cases/devtool.py | 10 +- ...Update-cmake_minimum_required-to-3.5.patch | 50 ++++ meta/recipes-bsp/u-boot/libubootenv_0.3.6.bb | 4 +- ...red-CMake-version-to-3.5-to-allow-bu.patch | 41 ++++ meta/recipes-core/musl/musl-locales_git.bb | 4 +- ...mum_required-to-3.13-to-avoid-warnin.patch | 47 ++++ meta/recipes-devtools/apt/apt_2.6.1.bb | 1 + ...native_3.31.6.bb => cmake-native_4.0.3.bb} | 6 +- meta/recipes-devtools/cmake/cmake.inc | 8 +- ...mpilerABI-Strip-pipe-from-compile-fl.patch | 63 ----- ...xt2fs-ext2_fs.h-by-cmake-s-internal.patch} | 4 +- ...ng-undocumented-type-for-CURLOPT_NET.patch | 30 --- ...trary-characters-in-test-names-of-CT.patch | 202 ---------------- ...-CMakeLists.txt-disable-USE_NGHTTP2.patch} | 6 +- .../cmake/{cmake_3.31.6.bb => cmake_4.0.3.bb} | 1 - .../0001-Fix-libname-of-Libs.private.patch | 22 ++ ...ED_TARGET-for-3rd-party-dependencies.patch | 226 ++++++++++++++++++ ...-imported-targets-of-turned-off-depe.patch | 53 ++++ ...ds-without-Doxygen-being-present-wit.patch | 50 ++++ .../createrepo-c/createrepo-c_1.2.1.bb | 4 + ...libcomps-Support-builds-with-CMake-4.patch | 132 ++++++++++ .../libcomps/libcomps_0.1.21.bb | 1 + ...red-CMake-version-to-3.5-to-allow-bu.patch | 38 +++ meta/recipes-sato/webkit/libwpe_1.16.2.bb | 6 +- 25 files changed, 695 insertions(+), 316 deletions(-) create mode 100644 meta/recipes-bsp/u-boot/libubootenv/0001-Update-cmake_minimum_required-to-3.5.patch create mode 100644 meta/recipes-core/musl/musl-locales/0001-cmake-Bump-required-CMake-version-to-3.5-to-allow-bu.patch create mode 100644 meta/recipes-devtools/apt/apt/0001-Raise-cmake_minimum_required-to-3.13-to-avoid-warnin.patch rename meta/recipes-devtools/cmake/{cmake-native_3.31.6.bb => cmake-native_4.0.3.bb} (90%) delete mode 100644 meta/recipes-devtools/cmake/cmake/0001-CMakeDetermineCompilerABI-Strip-pipe-from-compile-fl.patch rename meta/recipes-devtools/cmake/cmake/{0005-Disable-use-of-ext2fs-ext2_fs.h-by-cmake-s-internal-.patch => 0001-Disable-use-of-ext2fs-ext2_fs.h-by-cmake-s-internal.patch} (90%) delete mode 100644 meta/recipes-devtools/cmake/cmake/0001-cmCurl-Avoid-using-undocumented-type-for-CURLOPT_NET.patch delete mode 100644 meta/recipes-devtools/cmake/cmake/0001-ctest-Allow-arbitrary-characters-in-test-names-of-CT.patch rename meta/recipes-devtools/cmake/cmake/{0001-CMakeLists.txt-disable-USE_NGHTTP2.patch => 0002-CMakeLists.txt-disable-USE_NGHTTP2.patch} (83%) rename meta/recipes-devtools/cmake/{cmake_3.31.6.bb => cmake_4.0.3.bb} (96%) create mode 100644 meta/recipes-devtools/createrepo-c/createrepo-c/0001-Fix-libname-of-Libs.private.patch create mode 100644 meta/recipes-devtools/createrepo-c/createrepo-c/0002-Use-IMPORTED_TARGET-for-3rd-party-dependencies.patch create mode 100644 meta/recipes-devtools/createrepo-c/createrepo-c/0003-Don-t-try-to-use-imported-targets-of-turned-off-depe.patch create mode 100644 meta/recipes-devtools/createrepo-c/createrepo-c/0004-cmake-Allow-builds-without-Doxygen-being-present-wit.patch create mode 100644 meta/recipes-devtools/libcomps/libcomps/0001-libcomps-Support-builds-with-CMake-4.patch create mode 100644 meta/recipes-sato/webkit/libwpe/0001-cmake-Bump-required-CMake-version-to-3.5-to-allow-bu.patch