So it can be built with compilers that default to the
newer C standard.

Signed-off-by: Lucas Stach <[email protected]>
---
 ...stdbool.h-instead-of-rolling-our-own.patch | 36 +++++++++++++++++++
 patches/memedit-0.9/series                    |  4 +++
 2 files changed, 40 insertions(+)
 create mode 100644 
patches/memedit-0.9/0001-use-stdbool.h-instead-of-rolling-our-own.patch
 create mode 100644 patches/memedit-0.9/series

diff --git 
a/patches/memedit-0.9/0001-use-stdbool.h-instead-of-rolling-our-own.patch 
b/patches/memedit-0.9/0001-use-stdbool.h-instead-of-rolling-our-own.patch
new file mode 100644
index 000000000000..5ba25a6da9ff
--- /dev/null
+++ b/patches/memedit-0.9/0001-use-stdbool.h-instead-of-rolling-our-own.patch
@@ -0,0 +1,36 @@
+From: Lucas Stach <[email protected]>
+Date: Sun, 14 Dec 2025 18:12:57 +0100
+Subject: [PATCH] use stdbool.h instead of rolling our own
+
+With C23 bool is now a proper keyword, so we can not use
+the check if bool is defined to gate our own fallback.
+
+Use stdbool.h instead to have bool types across different
+compiler versions.
+
+Signed-off-by: Lucas Stach <[email protected]>
+---
+ memedit_parser.h | 8 +-------
+ 1 file changed, 1 insertion(+), 7 deletions(-)
+
+diff --git a/memedit_parser.h b/memedit_parser.h
+index c5db019b7cde..bed7544a789e 100644
+--- a/memedit_parser.h
++++ b/memedit_parser.h
+@@ -14,15 +14,9 @@
+ **
+ 
******************************************************************************/
+ 
++#include <stdbool.h>
+ #include <stdio.h>
+ 
+-#ifndef bool
+-typedef enum bool_t
+-{
+-  false = 0, true
+-} bool;
+-#endif
+-
+ /* customized structure for command line parameters */
+ struct arg_t
+ {
diff --git a/patches/memedit-0.9/series b/patches/memedit-0.9/series
new file mode 100644
index 000000000000..4c98424f3381
--- /dev/null
+++ b/patches/memedit-0.9/series
@@ -0,0 +1,4 @@
+# generated by git-ptx-patches
+#tag:base --start-number 1
+0001-use-stdbool.h-instead-of-rolling-our-own.patch
+# 84c619bd32bb289e17dd64b996d9ffb8  - git-ptx-patches magic
-- 
2.47.3


Reply via email to