scripts/libc: do not build add-ons by default

Currently, no --enable-add-ons option is passed to libc configure when
"$(do_libc_add_ons_list ,)" is empty, which makes configure automatically search
for present add-ons. In that case, all present add-ons are built, although
no add-on was selected by the user in the config. Moreover, this can make the
configure fail if some non-standard add-ons like eglibc-localedef are present.

This behavior also leads to an inconsistency from a user point of view between
the following cases:
- LIBC_ADDONS_LIST="", LIBC_GLIBC_USE_PORTS=n and THREADS="none" in the config,
which makes "$(do_libc_add_ons_list ,)" return "", so all present add-ons
are built.
- LIBC_ADDONS_LIST="", LIBC_GLIBC_USE_PORTS=n and THREADS!="none" in the
config, which makes "$(do_libc_add_ons_list ,)" return the add-on supporting
the chosen threading implementation, e.g. "nptl", so only this add-on is
built.

This patch disables the building of all add-ons in that case.

It is still possible to build all present add-ons by adding --enable-add-ons to
LIBC_GLIBC_EXTRA_CONFIG_ARRAY.

Signed-off-by: "Benoît THÉBAUDEAU" <benoit.thebaudeau@advansee.com>

# Build script for libtool

CT_LIBTOOL_VERSION=2.2.6b

do_companion_tools_libtool_get() {

    CT_GetFile "libtool-${CT_LIBTOOL_VERSION}" \

               {ftp,http}://ftp.gnu.org/gnu/libtool

}

do_companion_tools_libtool_extract() {

    CT_Extract "libtool-${CT_LIBTOOL_VERSION}"

    CT_DoExecLog ALL chmod -R u+w "${CT_SRC_DIR}/libtool-${CT_LIBTOOL_VERSION}"

    CT_Patch "libtool" "${CT_LIBTOOL_VERSION}"

}

do_companion_tools_libtool_build() {

    CT_DoStep EXTRA "Installing libtool"

    mkdir -p "${CT_BUILD_DIR}/build-libtool"

    CT_Pushd "${CT_BUILD_DIR}/build-libtool"

    CT_DoExecLog CFG \

    "${CT_SRC_DIR}/libtool-${CT_LIBTOOL_VERSION}/configure" \

        --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"

    CT_DoExecLog ALL make

    CT_DoExecLog ALL make install

    CT_Popd

    CT_EndStep

}