8996fedefb
We unconditionally configure asterisk with --with-crypt, so the build currently fails under glibc since it removed crypt in 2.39, and we explicitly remove it from external toolchains as well, whatever the version, causing build failures such as: checking for mandatory modules: OPENSSL BKTR CRYPT ILBC JANSSON LIBEDIT LIBJWT LIBXML2 PJPROJECT SQLITE3 ZLIB... fail configure: *** configure: *** The CRYPT installation appears to be missing or broken. configure: *** Either correct the installation, or run configure configure: *** including --without-crypt. Fixing this could be done in two ways: either make libxcrypt a mandatory dependency under glibc, and continue unconditionally enabling crypt support, or only enable crypt support when libxcrypt is available or this was a non-glibc toolchain. We chose the first option, to keep the existing behaviour (crypt support is always enabled), to be aligned with other packages (libxcrypt is selected under glibc toolchains), and because it is also the simplest. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> |
||
---|---|---|
.. | ||
0001-sounds-do-not-download-and-check-sha1s.patch | ||
0002-configure-fix-detection-of-libcrypt.patch | ||
0003-build-ensure-target-directory-for-modules-exists.patch | ||
0004-install-samples-need-the-data-files.patch | ||
0005-res-stasis-control.c-include-signal.h.patch | ||
asterisk.hash | ||
asterisk.mk | ||
Config.in |