public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: [PATCH 1/2] newlib: drop unused cache vars from Makefiles
Date: Tue,  1 Feb 2022 21:52:55 -0500	[thread overview]
Message-ID: <20220202025256.32179-1-vapier@gentoo.org> (raw)
In-Reply-To: <YfO69GDRoDRZmmQb@vapier>

These aren't used in any of the makefiles, so there's no point in
exporting these.  These are only checked in the configure script.
---
 newlib/Makefile.in  | 2 --
 newlib/configure    | 8 ++------
 newlib/configure.ac | 2 --
 3 files changed, 2 insertions(+), 10 deletions(-)

diff --git a/newlib/Makefile.in b/newlib/Makefile.in
index d2a0d4422f9a..5d49279ce48b 100644
--- a/newlib/Makefile.in
+++ b/newlib/Makefile.in
@@ -407,8 +407,6 @@ htmldir = @htmldir@
 includedir = @includedir@
 infodir = @infodir@
 install_sh = @install_sh@
-libc_cv_cc_loop_to_function = @libc_cv_cc_loop_to_function@
-libc_cv_initfinit_array = @libc_cv_initfinit_array@
 libdir = @libdir@
 libexecdir = @libexecdir@
 libm_machine_dir = @libm_machine_dir@
diff --git a/newlib/configure b/newlib/configure
index 65b93630315e..ca8953933cda 100755
--- a/newlib/configure
+++ b/newlib/configure
@@ -636,8 +636,6 @@ LTLIBOBJS
 LIBOBJS
 HAVE_LONG_DOUBLE_FALSE
 HAVE_LONG_DOUBLE_TRUE
-libc_cv_cc_loop_to_function
-libc_cv_initfinit_array
 NEWLIB_PATCHLEVEL_VERSION
 NEWLIB_MINOR_VERSION
 NEWLIB_MAJOR_VERSION
@@ -12008,7 +12006,7 @@ else
   lt_dlunknown=0; lt_dlno_uscore=1; lt_dlneed_uscore=2
   lt_status=$lt_dlunknown
   cat > conftest.$ac_ext <<_LT_EOF
-#line 12011 "configure"
+#line 12009 "configure"
 #include "confdefs.h"
 
 #if HAVE_DLFCN_H
@@ -12114,7 +12112,7 @@ else
   lt_dlunknown=0; lt_dlno_uscore=1; lt_dlneed_uscore=2
   lt_status=$lt_dlunknown
   cat > conftest.$ac_ext <<_LT_EOF
-#line 12117 "configure"
+#line 12115 "configure"
 #include "confdefs.h"
 
 #if HAVE_DLFCN_H
@@ -13300,7 +13298,6 @@ rm -f conftest*
 fi
 { $as_echo "$as_me:${as_lineno-$LINENO}: result: $libc_cv_initfinit_array" >&5
 $as_echo "$libc_cv_initfinit_array" >&6; }
-
 if test $libc_cv_initfinit_array = yes; then
 
 $as_echo "#define _HAVE_INITFINI_ARRAY 1" >>confdefs.h
@@ -13341,7 +13338,6 @@ $as_echo "#define _HAVE_CC_INHIBIT_LOOP_TO_LIBCALL 1" >>confdefs.h
 fi
 
 
-
   { $as_echo "$as_me:${as_lineno-$LINENO}: checking for long double" >&5
 $as_echo_n "checking for long double... " >&6; }
 if ${ac_cv_type_long_double+:} false; then :
diff --git a/newlib/configure.ac b/newlib/configure.ac
index c164e5a6494f..ce36ea19ac10 100644
--- a/newlib/configure.ac
+++ b/newlib/configure.ac
@@ -656,7 +656,6 @@ else
   libc_cv_initfinit_array=no
 fi
 rm -f conftest*])
-AC_SUBST(libc_cv_initfinit_array)
 if test $libc_cv_initfinit_array = yes; then
   AC_DEFINE(_HAVE_INITFINI_ARRAY, 1, [Define if the linker supports .preinit_array/.init_array/.fini_array sections.])
 fi
@@ -678,7 +677,6 @@ rm -f conftest*])
 if test $libc_cv_cc_loop_to_function = yes; then
   AC_DEFINE(_HAVE_CC_INHIBIT_LOOP_TO_LIBCALL, 1, [Define if compiler supports -fno-tree-loop-distribute-patterns.])
 fi
-AC_SUBST(libc_cv_cc_loop_to_function)
 
 AC_TYPE_LONG_DOUBLE
 dnl Export the setting for our installed headers to check.
-- 
2.34.1


  parent reply	other threads:[~2022-02-02  2:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  9:44 newlib_cv_ vs libc_cv_ autoconf cache vars prefix Mike Frysinger
2022-01-31 14:17 ` Corinna Vinschen
2022-02-01  3:12   ` Mike Frysinger
2022-02-01 14:55     ` Corinna Vinschen
2022-02-02  2:52 ` Mike Frysinger [this message]
2022-02-02  2:52   ` [PATCH 2/2] newlib: rename libc_cv_ prefix to newlib_cv_ Mike Frysinger
2022-02-03 12:08   ` [PATCH 1/2] newlib: drop unused cache vars from Makefiles Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220202025256.32179-1-vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=newlib@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).