From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit] package/yaml-cpp: bump version to 0.9.0
Date: Wed, 29 Jul 2026 21:58:40 +0200 [thread overview]
Message-ID: <20260729200548.538268B500@busybox.osuosl.org> (raw)
commit: https://gitlab.com/buildroot.org/buildroot/-/commit/a19e6cfe63064fb827b6234142374accd0317846
branch: https://gitlab.com/buildroot.org/buildroot/-/tree/master
For change log, see:
https://github.com/jbeder/yaml-cpp/releases/tag/yaml-cpp-0.9.0
Drop upstream patches.
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
[Julien: add link to change log in commit log]
Signed-off-by: Julien Olivain <ju.o@free.fr>
---
...1-emitterutils-Explicitly-include-cstdint.patch | 42 ----------------------
...policy-range-to-avoid-deprecation-warning.patch | 26 --------------
package/yaml-cpp/yaml-cpp.hash | 2 +-
package/yaml-cpp/yaml-cpp.mk | 4 +--
4 files changed, 3 insertions(+), 71 deletions(-)
diff --git a/package/yaml-cpp/0001-emitterutils-Explicitly-include-cstdint.patch b/package/yaml-cpp/0001-emitterutils-Explicitly-include-cstdint.patch
deleted file mode 100644
index e3dc308a2f..0000000000
--- a/package/yaml-cpp/0001-emitterutils-Explicitly-include-cstdint.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-From 7b469b4220f96fb3d036cf68cd7bd30bd39e61d2 Mon Sep 17 00:00:00 2001
-From: Christopher Fore <csfore@posteo.net>
-Date: Wed, 14 Aug 2024 21:02:32 -0400
-Subject: [PATCH] emitterutils: Explicitly include <cstdint>
-
-GCC 15 will no longer include it by default, resulting in build
-failures in projects that do not explicitly include it.
-
-Error:
-src/emitterutils.cpp:221:11: error: 'uint16_t' was not declared in this scope
- 221 | std::pair<uint16_t, uint16_t> EncodeUTF16SurrogatePair(int codePoint) {
- | ^~~~~~~~
-src/emitterutils.cpp:13:1: note: 'uint16_t' is defined in header '<cstdint>';
-this is probably fixable by adding '#include <cstdint>'
- 12 | #include "yaml-cpp/null.h"
- +++ |+#include <cstdint>
- 13 | #include "yaml-cpp/ostream_wrapper.h"
-
-Tests pass.
-
-Closes: #1307
-See-also: https://gcc.gnu.org/pipermail/gcc-cvs/2024-August/407124.html
-See-also: https://bugs.gentoo.org/937412
-Signed-off-by: Christopher Fore <csfore@posteo.net>
-
-Upstream: https://github.com/jbeder/yaml-cpp/commit/7b469b4220f96fb3d036cf68cd7bd30bd39e61d2
-
-Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
----
- src/emitterutils.cpp | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/src/emitterutils.cpp b/src/emitterutils.cpp
-index fc41011a5..f801b1d0c 100644
---- a/src/emitterutils.cpp
-+++ b/src/emitterutils.cpp
-@@ -1,4 +1,5 @@
- #include <algorithm>
-+#include <cstdint>
- #include <iomanip>
- #include <sstream>
-
diff --git a/package/yaml-cpp/0002-Specify-CMake-policy-range-to-avoid-deprecation-warning.patch b/package/yaml-cpp/0002-Specify-CMake-policy-range-to-avoid-deprecation-warning.patch
deleted file mode 100644
index 6ab3df96cf..0000000000
--- a/package/yaml-cpp/0002-Specify-CMake-policy-range-to-avoid-deprecation-warning.patch
+++ /dev/null
@@ -1,26 +0,0 @@
-From c2680200486572baf8221ba052ef50b58ecd816e Mon Sep 17 00:00:00 2001
-From: Craig Scott <craig.scott@crascit.com>
-Date: Thu, 17 Aug 2023 08:54:05 +1000
-Subject: [PATCH] Specify CMake policy range to avoid deprecation warning
- (#1211)
-
-Upstream: https://github.com/jbeder/yaml-cpp/commit/c2680200486572baf8221ba052ef50b58ecd816e
-
-Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
----
- CMakeLists.txt | 5 +++--
- 1 file changed, 3 insertions(+), 2 deletions(-)
-
-diff --git a/CMakeLists.txt b/CMakeLists.txt
-index 46dc18059..1ae92e2b7 100644
---- a/CMakeLists.txt
-+++ b/CMakeLists.txt
-@@ -1,5 +1,6 @@
--# 3.5 is actually available almost everywhere, but this a good minimum
--cmake_minimum_required(VERSION 3.4)
-+# 3.5 is actually available almost everywhere, but this a good minimum.
-+# 3.14 as the upper policy limit avoids CMake deprecation warnings.
-+cmake_minimum_required(VERSION 3.4...3.14)
-
- # enable MSVC_RUNTIME_LIBRARY target property
- # see https://cmake.org/cmake/help/latest/policy/CMP0091.html
diff --git a/package/yaml-cpp/yaml-cpp.hash b/package/yaml-cpp/yaml-cpp.hash
index 92bf65d2f7..321f932df4 100644
--- a/package/yaml-cpp/yaml-cpp.hash
+++ b/package/yaml-cpp/yaml-cpp.hash
@@ -1,3 +1,3 @@
# locally computed
-sha256 fbe74bbdcee21d656715688706da3c8becfd946d92cd44705cc6098bb23b3a16 yaml-cpp-0.8.0.tar.gz
+sha256 25cb043240f828a8c51beb830569634bc7ac603978e0f69d6b63558dadefd49a yaml-cpp-0.9.0.tar.gz
sha256 aa6fcc27be034e41e21dd832f9175bfe694a48491d9e14ff0fa278e19ad14f1b LICENSE
diff --git a/package/yaml-cpp/yaml-cpp.mk b/package/yaml-cpp/yaml-cpp.mk
index c259f1e531..b963dba094 100644
--- a/package/yaml-cpp/yaml-cpp.mk
+++ b/package/yaml-cpp/yaml-cpp.mk
@@ -4,8 +4,8 @@
#
################################################################################
-YAML_CPP_VERSION = 0.8.0
-YAML_CPP_SITE = $(call github,jbeder,yaml-cpp,$(YAML_CPP_VERSION))
+YAML_CPP_VERSION = 0.9.0
+YAML_CPP_SITE = $(call github,jbeder,yaml-cpp,yaml-cpp-$(YAML_CPP_VERSION))
YAML_CPP_INSTALL_STAGING = YES
YAML_CPP_LICENSE = MIT
YAML_CPP_LICENSE_FILES = LICENSE
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2026-07-29 20:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260729200548.538268B500@busybox.osuosl.org \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
/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