Fixed
Created: Jan 27, 2015
Updated: Sep 8, 2018
Resolved Date: Jan 27, 2015
Previous ID: LIN6-9338
Found In Version: 7.0
Fix Version: 7.0.0.2
Severity: Standard
Applicable for: Wind River Linux 7
Component/s: Build & Config
The following two issues have been observed with ldconfig.
The --enable-ldconfig=no option to configure seems to be ignored and the resulting local.conf file always has
USE_LDCONFIG = "1"
One can trace the problem to the following bit of code in the configure script:
# Process ENABLE_RECONFIG or --enable-ldconfig
echo "# Enable ldconfig" >>$local_conf
if [ X$ENABLE_RECONFIG != X0 -o X"$enable_ldconfig" = Xyes ] ; then
echo "USE_LDCONFIG = \"1\"" >>$local_conf
else
echo "USE_LDCONFIG = \"0\"" >>$local_conf
fi
echo "" >>$local_conf
As the $ENABLE_RECONFIG seems to be unrelated to --enable-ldconfig and is not set it always passes, whatever the value of $enable_ldconfig.
After manually setting USE_LDCONFIG = "0" in local.conf there is still a problem. Building the platform project I noticed that /etc/ld.so.cache is still created, when it should not because ldconfig is not called upon library installation and so the cache will become unsynced after a lib is updated with a different minor version. So the cache should not be created during image creation or should be removed at the end when USE_LDCONFIG is "0".
$ENABLE_RECONFIG is not set anywhere in the script, nor the calling configure script within the wrlinux-7 install, so this variable does not do anything.
What --enable-reconfig sets is $enable_reconfig, but that is not tested in the code handling the USE_LDCONFIG setting.
configure --enable-board=qemux86 --enable-rootfs=glibc_small --enable-kernel=standard --enable-reconfig=yes --enable-ldconfig=no
$ grep LDCONFIG local.conf
USE_LDCONFIG = "1"
