Bug 10486

Summary: libintl*.so should be in gettext-runtime when using musl
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Gianluigi Tiesi <sherpya>
Component: coreAssignee: Jussi Kukkonen <jku>
Status: RESOLVED OBSOLETE QA Contact:
Severity: normal    
Priority: Medium CC: meta.mr.watcher, meta.watcher, richard.purdie, sherpya
Version: 2.1.2   
Target Milestone: 2.1.3   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Gianluigi Tiesi 2016-10-22 01:52:06 UTC
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
Comment 1 Gianluigi Tiesi 2016-10-22 01:58:01 UTC
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?
Comment 2 Jussi Kukkonen 2016-10-28 09:52:22 UTC
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...
Comment 3 Jussi Kukkonen 2016-12-07 09:52:56 UTC
Setting target to 2.1.3 based on my previous comment.
Comment 4 Richard Purdie 2017-07-06 15:31:40 UTC
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.