10486 2016-10-22 01:52:06 +0000 libintl*.so should be in gettext-runtime when using musl 2017-07-06 15:31:40 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 2.1.2 All Multiple RESOLVED OBSOLETE Medium normal 2.1.3 1 sherpya jku meta.mr.watcher meta.watcher richard.purdie sherpya --- --- No (bug/feature does not impact docs) oldest_to_newest 67470 0 sherpya 2016-10-22 01:52:06 +0000 I see this line in the gettext recipe: FILES_gettext-runtime_append_libc-uclibc = " ${libdir}/libintl.so.* \ ${libdir}/charset.alias \ I had to add this one in my build because libintl so is packaged in gettext and not in gettext-runtime (this increasing file image size) FILES_gettext-runtime_append_libc-musl += "${libdir}/libintl.so.*" looks like there is no charset.alias files 67471 1 sherpya 2016-10-22 01:58:01 +0000 I also get this (I've disabled nls) WARNING: python-2.7.11-r1 do_package_qa: QA Issue: python-codecs rdepends on gettext-runtime, but it isn't a build dependency, missing gettext in DEPENDS or PACKAGECONFIG? [build-deps] that is ok for me (before was picking gettext instead), but gettext class shouldn't avoid this warning? 67715 2 jku 2016-10-28 09:52:22 +0000 I'm pretty sure this is not applicable to 2.3 and 2.2: as far as I can see gettext has been fixed to assume that the gettext implementation in musl is compatible and that it does not have to build (among other things) libintl. Assuming the above is correct, do we want to change this for 2.1? backporting the gettext changes sounds kind of drastic -- essentially swapping the gettext implementation after release. The suggested packaging change might be more reasonable maybe... 68892 3 jku 2016-12-07 09:52:56 +0000 Setting target to 2.1.3 based on my previous comment. 74830 4 richard.purdie 2017-07-06 15:31:40 +0000 If people want these changes in older releases we would need patches to be proposed, this hasn't happened and krogoth is now getting quite old. Resolving as obsolete as the issue isn't in master.