Re: [OE-core] [scarthgap][PATCH 5/6] elfutils: don't add -Werror to avoid discarded-qualifiers

Martin Jansa
2026-03-28T08:37:35Z

On Sat, Mar 28, 2026 at 1:07 AM Yoann Congal <yoann.congal@smile.fr> wrote:
>
> On Thu Mar 26, 2026 at 7:14 PM CET, Martin Jansa via lists.openembedded.org wrote:
> > From: Martin Jansa <martin.jansa@gmail.com>
> >
> > With glibc-2.43 on host elfutils-native fails with:
> > elfutils-0.191/libcpu/riscv_disasm.c:1259:46: error: initialization discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
> >
> > elfutils-0.194 in master doesn't have this issue thanks to this patch avoiding -Werror from:
> > https://git.openembedded.org/openembedded-core/commit/?id=1d6ac3c811798732e6addc798656bbe104661d77
> >
> > Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
> > ---
>
> Hello
>
> Isn't this patch (and 6/6) also needed on whinlatter?
> Can you send what is needed from series to whinlatter please?

Hi, I've asked about supporting hosts with glibc-2.43 in whinlatter
and Paul and Richard were concerned about the impact and whether it's
worth it considering that whinlatter will be EOL relatively soon.

I have some changes for whinlatter already, but it needs more fixes to
build image (m4 and gettext native are failing there), while with
these 6 in scarthgap I was able to build whole image already.

There is one more issue with latest ubuntu-26.04 (after updating
docker image to latest last week) which isn't solved by these 6
changes - libcrypt-dev is no longer installed as a dependency in my
minimal docker image, leading the python3-native failing to build
crypt and shadow-native failing to find libcrypt - I have explicitly
added it to Dockerfile to fix this one as virtual/crypt-native is in
ASSUME_PROVIDED and not sure if we want to use xcrypt-native to avoid
that.

Corresponding IRC log:
https://irc.yoctoproject.org/%23yocto.2026-03-25.log.html

JaMa paulbarker: Hi, any plans for supporting ubuntu-26.04 with glibc
2.43 on host? We will need at least new uninative from master,
m4-native, gettext-native fixes (instead of upgrades from master) and
probably more, I can help with that if there is consensus to get them
merged eventually 10:01

JaMa I mean for whinlatter branch, surprisingly older m4-native in
scarthgap doesn't fail with glibc 2.43 on host 10:02

paulbarker JaMa: I think it usually comes down to how invasive the
needed changes are 10:02

JaMa https://git.openembedded.org/openembedded-core/commit/?id=28552a7b6c94060c7ab3899619ab8afb74124d02
https://git.openembedded.org/openembedded-core/commit/?id=7d35b0e7929d666af783db835a3a809f8f6ce429
https://git.openembedded.org/openembedded-core/commit/?id=c1fb515f2a88fa0a0e95529afc07a99db001af0e
would be the start, then I can extract just the glibc fix from 10:05
JaMa https://git.openembedded.org/openembedded-core/commit/?id=97dd558277ea48e2161f389d6458517da6e04e4a
and similarly from
https://git.openembedded.org/openembedded-core/commit/?id=0ed7b56814d8337d1bd97cd2a4460065dba79207
that should be enough to build minimal image IIRC 10:05

RP paulbarker: I guess whinlatter is to be discontinued soon too which
is probably part of the reason for the question 10:05

paulbarker JaMa: I think we need to wait until 26.04 is out, then look
at whether we can easily support it in wrynose/scarthgap 10:06

paulbarker As RP says, whinlatter will be EOL, so will kirkstone 10:06

JaMa OK, won't offer my help until someone looks :) I can switch to
bit older 26.04 snapshot (the glibc was upgraded for 26.04 in last
week) 10:08

paulbarker JaMa: Sorry, I don't mean to sound dismissive. We're just
focused on the last features for the LTS release and I don't want us
to take on too much more until they're done 10:18

RP JaMa: your help is definitely welcome, it is just a question of how
much work we should do on whinlatter now 10:28

JaMa RP: paulbarker: thanks, I have started with scarthgap issues, m4
and gettext surprisingly doesn't fail there so it might be just the
first 3 commits I've mentioned, doing the rebuild from scratch now

Cheers,