From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: [PATCH] newlib: update nds32 configure checks
Date: Sat, 22 Jan 2022 20:39:33 -0500 [thread overview]
Message-ID: <20220123013933.911-1-vapier@gentoo.org> (raw)
This subdir doesn't link any code, so there's no need to require
AC_NO_EXECUTABLES, and no other dir uses this either. Punt it.
The two tests in here are using compile tests to look for some
preprocessor defines, but we don't need to compile the code,
just preprocess it. So switch to AC_PREPROC_IFELSE.
---
newlib/libm/machine/nds32/Makefile.in | 1 +
newlib/libm/machine/nds32/configure | 266 +++++++++++++++++--------
newlib/libm/machine/nds32/configure.ac | 5 +-
3 files changed, 186 insertions(+), 86 deletions(-)
mode change 100644 => 100755 newlib/libm/machine/nds32/configure
diff --git a/newlib/libm/machine/nds32/configure.ac b/newlib/libm/machine/nds32/configure.ac
index 7d49c9ae20bf..d4c5f49a2625 100644
--- a/newlib/libm/machine/nds32/configure.ac
+++ b/newlib/libm/machine/nds32/configure.ac
@@ -11,8 +11,7 @@ NEWLIB_CONFIGURE(../../..)
dnl Use builtin macro to detect if FPU extension support is on.
-AC_NO_EXECUTABLES
-AC_COMPILE_IFELSE([AC_LANG_PROGRAM(
+AC_PREPROC_IFELSE([AC_LANG_PROGRAM(
[[#if (__NDS32_EXT_FPU_SP__)
warning: Has nds32 FPU SP extension support
#endif
@@ -21,7 +20,7 @@ warning: Has nds32 FPU SP extension support
[has_nds32_fpu_sp="yes"])
AM_CONDITIONAL(HAS_NDS32_FPU_SP, test "$has_nds32_fpu_sp" = "yes")
-AC_COMPILE_IFELSE([AC_LANG_PROGRAM(
+AC_PREPROC_IFELSE([AC_LANG_PROGRAM(
[[#if (__NDS32_EXT_FPU_DP__)
warning: Has nds32 FPU DP extension support
#endif
--
2.34.1
next reply other threads:[~2022-01-23 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 1:39 Mike Frysinger [this message]
2022-01-23 5:25 ` [PATCH] newlib: update preprocessor " Mike Frysinger
2022-01-24 16:39 ` Corinna Vinschen
2022-01-24 16:39 ` [PATCH] newlib: update nds32 " 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=20220123013933.911-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).