[meta-oe][PATCH] libgee: downgrade incompatible-pointer-types back to warning

[meta-oe][PATCH] libgee: downgrade incompatible-pointer-types back to warning

[Markus Volk]

Workaround to fix build with gcc14

Signed-off-by: Markus Volk <f_l_k@t-online.de>
---
 meta-oe/recipes-devtools/libgee/libgee_0.20.6.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta-oe/recipes-devtools/libgee/libgee_0.20.6.bb b/meta-oe/recipes-devtools/libgee/libgee_0.20.6.bb
index 0ed6e8235..4f9099ff0 100644
--- a/meta-oe/recipes-devtools/libgee/libgee_0.20.6.bb
+++ b/meta-oe/recipes-devtools/libgee/libgee_0.20.6.bb
@@ -11,6 +11,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
 GNOMEBASEBUILDCLASS = "autotools"
 inherit gnomebase vala gobject-introspection
 
+CFLAGS += "-Wno-incompatible-pointer-types"
+
 do_configure:prepend() {
     MACROS="libtool.m4 lt~obsolete.m4 ltoptions.m4 ltsugar.m4 ltversion.m4"
     for i in ${MACROS}; do
-- 
2.45.1

Re: [oe] [meta-oe][PATCH] libgee: downgrade incompatible-pointer-types back to warning

[Khem Raj]

On Sun, Jun 9, 2024 at 11:44 AM Markus Volk via lists.openembedded.org
<f_l_k=t-online.de@lists.openembedded.org> wrote:
>
> Workaround to fix build with gcc14
>
> Signed-off-by: Markus Volk <f_l_k@t-online.de>
> ---
>  meta-oe/recipes-devtools/libgee/libgee_0.20.6.bb | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/meta-oe/recipes-devtools/libgee/libgee_0.20.6.bb b/meta-oe/recipes-devtools/libgee/libgee_0.20.6.bb
> index 0ed6e8235..4f9099ff0 100644
> --- a/meta-oe/recipes-devtools/libgee/libgee_0.20.6.bb
> +++ b/meta-oe/recipes-devtools/libgee/libgee_0.20.6.bb
> @@ -11,6 +11,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
>  GNOMEBASEBUILDCLASS = "autotools"
>  inherit gnomebase vala gobject-introspection
>
> +CFLAGS += "-Wno-incompatible-pointer-types"
> +

Is this in works upstream ? if not it will be good to atleast report it

>  do_configure:prepend() {
>      MACROS="libtool.m4 lt~obsolete.m4 ltoptions.m4 ltsugar.m4 ltversion.m4"
>      for i in ${MACROS}; do
> --
> 2.45.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#110783): https://lists.openembedded.org/g/openembedded-devel/message/110783
> Mute This Topic: https://lists.openembedded.org/mt/106580066/1997914
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: [oe] [meta-oe][PATCH] libgee: downgrade incompatible-pointer-types back to warning

[Markus Volk]

[-- Attachment #1: Type: text/plain, Size: 578 bytes --]

On Sun, Jun 9 2024 at 11:57:03 AM -07:00:00, Khem Raj 
<raj.khem@gmail.com> wrote:
> Is this in works upstream ? if not it will be good to atleast report 
> it

I had a look here and to me it seems like it needs to be to be fixed 
mostly in vala
<https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/l/libgee.md?ref_type=heads>


But that has been reported for various distributions, so I guess people 
are aware of the issue
<https://lists.opensuse.org/archives/list/bugs@lists.opensuse.org/message/7GKXU2QW6DCH6AJQ62PLFWDMRNTEM5FD/>
<https://bugs.gentoo.org/920315>



[-- Attachment #2: Type: text/html, Size: 1084 bytes --]

Re: [oe] [meta-oe][PATCH] libgee: downgrade incompatible-pointer-types back to warning

[Khem Raj]

On Sun, Jun 9, 2024 at 12:04 PM Markus Volk <f_l_k@t-online.de> wrote:
>
> On Sun, Jun 9 2024 at 11:57:03 AM -07:00:00, Khem Raj <raj.khem@gmail.com> wrote:
>
> Is this in works upstream ? if not it will be good to atleast report it
>
>
> I had a look here and to me it seems like it needs to be to be fixed mostly in vala
> https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/l/libgee.md?ref_type=heads
>
>
> But that has been reported for various distributions, so I guess people are aware of the issue
> https://lists.opensuse.org/archives/list/bugs@lists.opensuse.org/message/7GKXU2QW6DCH6AJQ62PLFWDMRNTEM5FD/
> https://bugs.gentoo.org/920315
>

OK cool. Would you mind sending a v2 with this info added as comment
perhaps in recipe
so someone working on it in future can try to remove it when fixed.