From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>
Subject: [PATCH] enchant2: Disable incompatible-pointer-types warning as error
Date: Wed, 8 May 2024 21:14:06 -0700 [thread overview]
Message-ID: <20240509041406.2977304-1-raj.khem@gmail.com> (raw)
This fixes build with GCC-14
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
meta/recipes-support/enchant/enchant2_2.7.2.bb | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-support/enchant/enchant2_2.7.2.bb b/meta/recipes-support/enchant/enchant2_2.7.2.bb
index 08998dd48fe..7e175852556 100644
--- a/meta/recipes-support/enchant/enchant2_2.7.2.bb
+++ b/meta/recipes-support/enchant/enchant2_2.7.2.bb
@@ -27,3 +27,7 @@ FILES:${PN} += " \
${libdir}/enchant-2 \
"
FILES:${PN}-staticdev += "${libdir}/enchant-2/*.a"
+
+#api.vala:43:18: error: assignment to 'gchar **' {aka 'char **'} from incompatible pointer type 'const gchar * const*' {aka 'const char * const*'} [-Wincompatible-pointer-types]
+
+CFLAGS += "-Wno-error=incompatible-pointer-types"
--
2.45.0
next reply other threads:[~2024-05-09 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 4:14 Khem Raj [this message]
2024-05-09 12:48 ` [OE-core] [PATCH] enchant2: Disable incompatible-pointer-types warning as error Ross Burton
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=20240509041406.2977304-1-raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).