On Tue, Feb 10, 2026 at 7:25 AM Alexander Kanavin <[email protected]> wrote: > > On Mon, 9 Feb 2026 at 19:23, Ankur Tyagi <[email protected]> wrote: > > > > - dropped mdcheck install patch to address reproducibility issue > > > > > > > EXTRA_OEMAKE = 'CHECK_RUN_DIR=0 CWFLAGS="" CXFLAGS="${CFLAGS}" > > > > SYSTEMD_DIR=${systemd_system_unitdir} \ > > > > BINDIR="${base_sbindir}" > > > > UDEVDIR="${nonarch_base_libdir}/udev" LDFLAGS="${LDFLAGS}" \ > > > > - SYSROOT="${STAGING_DIR_TARGET}" STRIP=' > > > > + SYSROOT="${STAGING_DIR_TARGET}" > > > > MISCDIR="${datadir}/${BPN}" STRIP=' > > > > > > > > > > This has merged, and unfortunately the same reproducibility issue > > > appeared in nightly master: > > > > > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/3317 > > > > > > The issue seems to be that sometimes the sed command to patch BINDIR > > > in mdcheck works, and sometimes it does not. I am baffled as to why > > > that would be, but we can't have such fails in master, so for now I'm > > > afraid this should be reverted. > > > > > > > yeah, that's odd. > > Let's revert it and I will spend some time understanding what's going on > > here. > > One idea is to try to catch the issue right when it happens, e.g. add > a test patch that greps the offending file for BINDIR, and if that's a > yes, then it loudly fails, stopping the build. We can take it into a > staging branch and then once it fails someone can look into why sed > didn't work. >
Thanks Alex, I will try it out in the coming days and send a patch to monitor the situation. > Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#230814): https://lists.openembedded.org/g/openembedded-core/message/230814 Mute This Topic: https://lists.openembedded.org/mt/117590273/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
