[OE-core] Should disabling features in glibc also disable the corresponding headers?
Tanu Kaskinen
tanu.kaskinen at linux.intel.com
Tue Apr 14 17:25:25 UTC 2015
Hello,
oe-core's version of glibc allows configuring out some libc features.
Currently, if a feature is disabled in glibc, glibc still installs the
header for that feature. This means that applications using glibc can't
rely on checking just the header presence in their configure scripts,
they also need to check whether the function implementation is present.
Is there some good reason why glibc works that way, or should glibc be
fixed so that disabling a feature disables the header too?
At least alsa-lib requires patching[1] for this reason, and I wouldn't
be surprised if there were many other similar cases in other packages.
[1]
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-multimedia/alsa/alsa-lib/Check-if-wordexp-function-is-supported.patch
--
Tanu
More information about the Openembedded-core
mailing list