From 78ceef25d64efeeb6067d1cb282a00466e637e2a Mon Sep 17 00:00:00 2001 From: Adhemerval Zanella Netto Date: Mon, 24 Jul 2023 14:22:27 -0300 Subject: configure: Remove --enable-all-warnings option The option is not activelly tested and has bitrotten, to fix it would require a lot of work and multiple fixes. A better option would to evaluate each option and enable the warning if it makes sense. Reviewed-by: Siddhesh Poyarekar --- configure | 11 ----------- 1 file changed, 11 deletions(-) (limited to 'configure') diff --git a/configure b/configure index 4ef387146d..eeb3ef49b8 100755 --- a/configure +++ b/configure @@ -705,7 +705,6 @@ libc_cv_nss_crypt build_crypt memory_tagging enable_werror -all_warnings force_install bindnow hardcoded_path_in_tests @@ -804,7 +803,6 @@ enable_static_nss enable_force_install enable_maintainer_mode enable_kernel -enable_all_warnings enable_werror enable_multi_arch enable_memory_tagging @@ -1478,7 +1476,6 @@ Optional Features: sometimes confusing) to the casual installer --enable-kernel=VERSION compile for compatibility with kernel not older than VERSION - --enable-all-warnings enable all useful warnings gcc can issue --disable-werror do not build with -Werror --enable-multi-arch enable single DSO with optimizations for multiple architectures @@ -4526,14 +4523,6 @@ else fi fi -# Check whether --enable-all-warnings was given. -if test ${enable_all_warnings+y} -then : - enableval=$enable_all_warnings; all_warnings=$enableval -fi - - - # Check whether --enable-werror was given. if test ${enable_werror+y} then : -- cgit 1.4.1