5964 2014-03-13 17:49:44 +0000 e2fsprogs: gettext mismatch failure with non-gplv3 builds 2014-04-01 17:02:09 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple RESOLVED FIXED Medium normal 1.6 M5 1 kergoth kergoth meta.mr.watcher meta.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 41203 0 kergoth 2014-03-13 17:49:44 +0000 Ever since the change to how aclocal files are copied (based on dependencies), target m4 macros seem to more reliably be used in preference to native (which they should), but in a non-gplv3 build, gettext is 0.16 while gettext-native is 0.18, causing a 0.16 po.m4 to be used with our 0.18 po/Makefile.in.in files, causing at least some failed builds, including e2fsprogs. I think the best way to work around this situation, assuming we're stuck using 0.16 target gettext, which I think we are, would be to just drop the target gettext m4 macros from the sysroot. Anyone inheriting gettext will also dep on gettext-native, so will get the macros from the newer gettext-native recipe anyway. See https://github.com/MentorEmbedded/meta-mentor/pull/110 for the workaround we're using at Mentor at the moment to fix our currently broken non-gplv3 builds (INCOMPATIBLE_LICENSE = "LGPLv3 GPLv3"). 41336 1 sgw 2014-03-17 17:04:26 +0000 I think the suggested workaround might be the best choice, please go ahead and submitt a patch. 42059 2 kergoth 2014-04-01 17:02:09 +0000 The fix for this was merged to oe-core.