public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Martin Jansa" <martin.jansa@gmail.com>
Cc: <openembedded-core@lists.openembedded.org>,
	"Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>,
	"Richard Purdie" <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [whinlatter][PATCH 1/9] dtc: backport fix for build with glibc-2.43
Date: Fri, 10 Apr 2026 11:44:24 +0200	[thread overview]
Message-ID: <DHPDMAYQ3JM8.3MDZOUUD9PA02@smile.fr> (raw)
In-Reply-To: <CA+chaQfMPZ3266azx2veSiK4nwXDXMQ_i4RoiKQuKicaU-L0Jw@mail.gmail.com>

On Fri Apr 10, 2026 at 11:39 AM CEST, Martin Jansa wrote:
> On Fri, Apr 10, 2026 at 11:28 AM Yoann Congal <yoann.congal@smile.fr> wrote:
>>
>> On Fri Apr 10, 2026 at 11:09 AM CEST, Martin Jansa wrote:
>> > On Fri, Apr 10, 2026 at 9:42 AM Yoann Congal <yoann.congal@smile.fr> wrote:
>> >>
>> >> On Thu Apr 9, 2026 at 11:29 PM CEST, Martin Jansa wrote:
>> >> > On Thu, Apr 9, 2026 at 9:17 PM Yoann Congal <yoann.congal@smile.fr> wrote:
>> >> >>
>> >> >> On Thu Apr 9, 2026 at 5:28 PM CEST, Martin Jansa via lists.openembedded.org wrote:
>> >> >> > From: Martin Jansa <martin.jansa@gmail.com>
>> >> >> >
>> >> >> > glibc-2.43 isn't used in OE builds yet, but this fixes dtc-native:
>> >> >> > https://errors.yoctoproject.org/Errors/Details/903983/
>> >> >> >
>> >> >> > ../sources/dtc-1.7.2/libfdt/fdt_overlay.c: In function ‘overlay_fixup_phandle’:
>> >> >> > ../sources/dtc-1.7.2/libfdt/fdt_overlay.c:424:21: error: assignment discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
>> >> >> >   424 |                 sep = memchr(fixup_str, ':', fixup_len);
>> >> >> >       |                     ^
>> >> >> > ../sources/dtc-1.7.2/libfdt/fdt_overlay.c:434:21: error: assignment discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
>> >> >> >   434 |                 sep = memchr(name, ':', fixup_len);
>> >> >> >       |                     ^
>> >> >> > cc1: all warnings being treated as errors
>> >> >> >
>> >> >> > Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
>> >> >> > Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
>> >> >> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>> >> >> > ---
>> >> >>
>> >> >> Hello,
>> >> >>
>> >> >> I've started a whinlatter bringup build on the new Ubuntu 26.04 worker
>> >> >> with this series applied:
>> >> >> https://autobuilder.yoctoproject.org/valkyrie/#/builders/96/builds/23
>> >> >>
>> >> >> It got 2 errors (Other errors are most likely consequences of these ones):
>> >> >>
>> >> >> ERROR: shadow-native-4.18.0-r0 do_configure: configure failed:
>> >> >> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/96/builds/23/steps/12/logs/stdio line 6269:
>> >> >> | checking for crypt in -lcrypt... no
>> >> >> | configure: error: crypt() not found
>> >> >> | NOTE: The following config.log files may provide further information.
>> >> >> | NOTE: /srv/pokybuild/yocto-worker/bringup/build/build/tmp/work/x86_64-linux/shadow-native/4.18.0/build/config.log
>> >> >> | ERROR: configure failed
>> >> >> | WARNING: exit code 1 from a shell command.
>> >> >> NOTE: recipe shadow-native-4.18.0-r0: task do_configure: Failed
>> >> >
>> >> > Hello,
>> >> >
>> >> > for shadow please read
>> >> > https://lists.openembedded.org/g/openembedded-core/message/234119 the
>> >> > important part:
>> >> > "libcrypt-dev is no longer installed as a dependency in my minimal docker image"
>> >> > I guess it's now missing on your ubuntu-26.04 host as well.
>> >> > It used to be typically installed by build-essential -> libc6-dev ->
>> >> > libcrypt-dev but not anymore since 2.42-7:
>> >> >
>> >> > 25.10 questing with 2.42-0ubuntu3.1:
>> >> > https://packages.ubuntu.com/questing/libc6-dev
>> >> > 26.04 resolute with 2.43-2ubuntu1:
>> >> > https://packages.ubuntu.com/resolute/libc6-dev
>> >> >
>> >> > https://changelogs.ubuntu.com/changelogs/pool/main/g/glibc/glibc_2.43-2ubuntu1/changelog:
>> >> > ...
>> >> > glibc (2.42-7) unstable; urgency=medium
>> >> >
>> >> >   [ Aurelien Jarno ]
>> >> >   * debian/control.in/libc, debian/rules.d/debhelper.mk: drop libcrypt-dev
>> >> >     dependency from libc6-dev. Thanks to Helmut Grohne for proposing that,
>> >> >     doing an archive rebuild and filling the bug reports.
>> >> >   * debian/control.in/main, debian/sysdeps/linux.mk: enable SystemTap static
>> >> >     probes.
>> >> >   * debian/debhelper.in/libc-dev.NEWS: add a NEWS entry about the removal of
>> >> >     the obsolete termio interface.  Closes: #1124068.
>> >> >   * debian/rules.d/debhelper.mk: ensure that linker scripts work even when
>> >> >     /usr is unmerged.  Closes: #1120508
>> >> >   * debian/debhelper.in/libc-dev{,-alt}.lintian-overrides,
>> >> >     source/lintian-overrides, rules.d/debhelper.mk, salsa-ci.yml: drop
>> >> >     unpack-message-for-{orig,source} overrides, fixed in lintian 2.128.0.
>> >> >   * debian/control.in/main: drop Rules-Requires-Root: no, this is now the
>> >> >     default.
>> >> >   * debian/libc6.symbols.i386, debian/libc6-i386.symbols.{amd64,x32}: remove
>> >> >     the workaround for GLIBC_ABI_GNU_TLS.  Closes: #1122038.
>> >> >   * debian/control.in/{libc,i386}: ensure that libdpkg-perl is fixed wrt
>> >> >     GLIBC_ABI_GNU_TLS.
>> >> >
>> >> >  -- Aurelien Jarno <aurel32@debian.org>  Sun, 04 Jan 2026 10:07:24 +0100
>> >> > ...
>> >>
>> >> Hello,
>> >>
>> >> In that case, shouldn't we remove "virtual/crypt-native" from ASSUME_PROVIDED?
>> >> https://git.openembedded.org/openembedded-core/tree/meta/conf/bitbake.conf#n232
>> >>
>> >> I've tried it but then libxcrypt-native fails to build with:
>> >> | ../sources/libxcrypt-4.4.38/lib/crypt-gost-yescrypt.c: In function ‘_crypt_crypt_gost_yescrypt_rn’:
>> >> | ../sources/libxcrypt-4.4.38/lib/crypt-gost-yescrypt.c:134:16: error: initialization discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
>> >> |   134 |   char *hptr = strchr ((const char *) intbuf->retval + 3, '$');
>> >> |       |                ^~~~~~
>> >> | cc1: all warnings being treated as errors
>> >>
>> >> It looks like the fixes for that are on master but the patches don't
>> >> apply.
>> >>
>> >> Can you send an update series with those fixes?
>> >
>> >
>> > Patches for building libxcrypt-native? I still see
>> > virtual/crypt-native in ASSUME_PROVIDED in master, that's why I've
>> > added libcrypt-dev into the ubuntu-26.04 image at least until the same
>> > is resolved in wrynose/master. The same issue is in current master.
>>
>> (Sorry, our mails crossed)
>>
>> I discussed that with Paul. He suggested to add libcrypt-dev as a host
>> dependency instead (ie. what you describe). I agree (sorry about the
>> sudden change of heart).
>>
>> Can you send the yocto-docs patch to do this?
>
> Yes, done:
> https://lists.yoctoproject.org/g/docs/message/9213

Awesome, thanks!
Next, I will ask helpdesk to install libcrypt-dev on the ubuntu 26.04
worker and start the build with the added patch 
"virglrenderer: Fix build with glibc 2.43+"

-- 
Yoann Congal
Smile ECS



  reply	other threads:[~2026-04-10  9:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 15:28 [whinlatter][PATCH 1/9] dtc: backport fix for build with glibc-2.43 martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 2/9] pseudo: Add fix for glibc 2.43 martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 3/9] yocto-uninative: Update to 5.1 " martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 4/9] m4: backport 3 gnulib changes to fix build with glibc-2.43 on host martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 5/9] gettext: backport " martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 6/9] util-linux: backport fix to " martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 7/9] systemd: " martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 8/9] gcc: backport a fix for building with gcc-16 martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 9/9] binutils: backport patch to fix build with glibc-2.43 on host martin.jansa
2026-04-09 19:17 ` [OE-core] [whinlatter][PATCH 1/9] dtc: backport fix for build with glibc-2.43 Yoann Congal
2026-04-09 21:29   ` Martin Jansa
2026-04-10  7:41     ` Yoann Congal
2026-04-10  9:09       ` Martin Jansa
2026-04-10  9:28         ` Yoann Congal
2026-04-10  9:39           ` Martin Jansa
2026-04-10  9:44             ` Yoann Congal [this message]
2026-04-10 10:09               ` Martin Jansa
2026-04-10  9:19       ` Yoann Congal
     [not found]   ` <18A4CD91CED0CFD1.657799@lists.openembedded.org>
2026-04-10  6:14     ` Martin Jansa

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=DHPDMAYQ3JM8.3MDZOUUD9PA02@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=martin.jansa@gmail.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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