15291 2023-11-22 01:37:53 +0000 Non identical glib 2.0 schemas with multlib 2026-10-28 11:52:16 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 5.0 All Multiple NEW Medium normal 6.2 1 raj.khem ross.burton meta.mr.watcher meta.watcher randy.macleod ross.burton --- --- No (bug/feature does not impact docs) oldest_to_newest 97297 0 raj.khem 2023-11-22 01:37:53 +0000 When using distros with multilib enabled, the schemas for both 32-bit and 64-bit get computed separately but installed into same location at the end of rootfs and in some cases these compiled gschemas are not identical. To reproduce require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE:virtclass-multilib-lib32 = "x86" IMAGE_INSTALL:append = ' lib32-connman-gnome gtk4' MACHINE=qemux86-64 bitbake core-image-sato It results in ERROR: core-image-sato-1.0-r0 do_rootfs: Multilib check error: duplicate files /home/pokybuild/yocto-worker/multilib/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0/multilib/lib32/usr/share/glib-2.0/schemas/gschemas.compiled /home/pokybuild/yocto-worker/multilib/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0/rootfs/usr/share/glib-2.0/schemas/gschemas.compiled is not the same The reason why these are different is because normal rootfs now includes schema xml files from gtk4 and gtk+3 but 32bit rootfs contains only gtk+3 schemas. If I add "lib32-gtk4" into IMAGE_INSTALL then it becomes identical as expected.