Message-ID: <552D4D85.9010104@linux.intel.com>
Date: Tue, 14 Apr 2015 20:25:25 +0300
From: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: openembedded-core@lists.openembedded.org
Subject: Should disabling features in glibc also disable the corresponding headers?
Precedence: list
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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