From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [PATCH] libstdc++: Use AS_IF in configure.ac
Date: Thu, 1 Jun 2023 16:58:56 +0100 [thread overview]
Message-ID: <20230601155856.305565-1-jwakely@redhat.com> (raw)
Tested x86_64-linux. I'd appreciate a second set of eyeballs on this
before I push it.
-- >8 --
This ensures that anything that depends on AC_REQUIRE is hoisted out of
the conditional block.
The always-false test x"long_double_math_on_this_cpu" = x"yes" condition
is not altered by this commit, only changed to use the AS_IF syntax.
libstdc++-v3/ChangeLog:
* configure.ac: Use AS_IF.
* configure: Regenerate.
---
libstdc++-v3/configure | 1148 +++++++++++++++++++------------------
libstdc++-v3/configure.ac | 20 +-
2 files changed, 590 insertions(+), 578 deletions(-)
diff --git a/libstdc++-v3/configure.ac b/libstdc++-v3/configure.ac
index 0abe54e7b9a..f3bcf7affdd 100644
--- a/libstdc++-v3/configure.ac
+++ b/libstdc++-v3/configure.ac
@@ -266,7 +266,7 @@ AC_CHECK_HEADERS([linux/random.h], [], [],
AC_CHECK_HEADERS([xlocale.h])
# Only do link tests if native. Else, hardcode.
-if $GLIBCXX_IS_NATIVE; then
+AS_IF([$GLIBCXX_IS_NATIVE],[
# We can do more elaborate tests that assume a working linker.
CANADIAN=no
@@ -298,7 +298,7 @@ if $GLIBCXX_IS_NATIVE; then
# For iconv support.
AM_ICONV
-else
+],[
# This lets us hard-code the functionality we know we'll have in the cross
# target environment. "Let" is a sugar-coated word placed on an especially
@@ -330,7 +330,7 @@ else
# First, test for "known" system libraries. We may be using newlib even
# on a hosted environment.
- if test "x${with_newlib}" = "xyes"; then
+ AS_IF([test "x${with_newlib}" = "xyes"],[
os_include_dir="os/newlib"
AC_DEFINE(HAVE_HYPOT)
@@ -386,14 +386,14 @@ else
AC_DEFINE(HAVE_USLEEP)
;;
esac
- elif test "x$with_headers" != "xno"; then
+ ],[test "x$with_headers" != "xno" ],[
GLIBCXX_CROSSCONFIG
- fi
+ ])
# At some point, we should differentiate between architectures
# like x86, which have long double versions, and alpha/powerpc/etc.,
# which don't. For the time being, punt.
- if test x"long_double_math_on_this_cpu" = x"yes"; then
+ AS_IF([test x"long_double_math_on_this_cpu" = x"yes"],[
AC_DEFINE(HAVE_ACOSL)
AC_DEFINE(HAVE_ASINL)
AC_DEFINE(HAVE_ATAN2L)
@@ -417,8 +417,8 @@ else
AC_DEFINE(HAVE_SQRTL)
AC_DEFINE(HAVE_TANL)
AC_DEFINE(HAVE_TANHL)
- fi
-fi
+ ])
+])
# Check for _Unwind_GetIPInfo.
GCC_CHECK_UNWIND_GETIPINFO
@@ -449,7 +449,7 @@ case "$target" in
#error no need for long double compatibility
#endif
], [ac_ldbl_compat=yes], [ac_ldbl_compat=no])
- if test "$ac_ldbl_compat" = yes; then
+ AS_IF([test "$ac_ldbl_compat" = yes],[
AC_DEFINE([_GLIBCXX_LONG_DOUBLE_COMPAT],1,
[Define if compatibility should be provided for -mlong-double-64.])
port_specific_symbol_files="\$(top_srcdir)/config/os/gnu-linux/ldbl-extra.ver"
@@ -485,7 +485,7 @@ case "$target" in
fi
;;
esac
- fi
+ ])
esac
AC_SUBST(LONG_DOUBLE_COMPAT_FLAGS)
AC_SUBST(LONG_DOUBLE_128_FLAGS)
--
2.40.1
next reply other threads:[~2023-06-01 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 15:58 Jonathan Wakely [this message]
2023-06-06 15:30 ` Jonathan Wakely
2023-06-07 14:42 ` Hans-Peter Nilsson
2023-06-07 14:54 ` Jonathan Wakely
2023-06-07 14:56 ` Jonathan Wakely
2023-06-07 15:18 ` Andreas Schwab
2023-06-07 15:57 ` Jonathan Wakely
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=20230601155856.305565-1-jwakely@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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).