diff options
author | Mike Frysinger <vapier@gentoo.org> | 2022-01-28 13:12:54 +0300 |
---|---|---|
committer | Mike Frysinger <vapier@gentoo.org> | 2022-02-01 06:21:17 +0300 |
commit | 4b0e66093c0b48d5c363cf17c45ad9bf88ae526c (patch) | |
tree | e543410a0b4c62389af37ecfc3bb16f38b447a33 /newlib/libc/configure.ac | |
parent | 6a59fc444b46681b59ce3152cfbd3c9e024455fa (diff) |
newlib: fix preprocessor checks
Restore the call to AC_NO_EXECUTABLES -- I naively assumed in commit
2e9aa5f56cc26a411014a7f788423c670cfb5646 ("newlib: update preprocessor
configure checks") that checking for a preprocessor would not involve
linking code. Unfortunately, autoconf will implicitly check that the
compiler "works" before allowing it to be used, and that involves a
link test, and that fails because newlib provides the C library which
is needed to pass a link test.
There is some code in NEWLIB_CONFIGURE specifically to help mitigate
these, but it's not kicking in here for some reason, so let's just add
the AC_NO_EXECUTABLES call back until we can unwind that custom logic.
Additionally, we have to call AC_PROG_CPP explicitly. This was being
invoked later on, but only in the use_libtool=yes codepath, and that
is almost never enabled.
Diffstat (limited to 'newlib/libc/configure.ac')
-rw-r--r-- | newlib/libc/configure.ac | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/newlib/libc/configure.ac b/newlib/libc/configure.ac index 5d4dc7bf5..4a0160a57 100644 --- a/newlib/libc/configure.ac +++ b/newlib/libc/configure.ac @@ -45,7 +45,9 @@ AC_ARG_ENABLE(newlib-retargetable-locking, esac],[newlib_retargetable_locking=no]) AM_CONDITIONAL(NEWLIB_RETARGETABLE_LOCKING, test x$newlib_retargetable_locking = xyes) +AC_NO_EXECUTABLES NEWLIB_CONFIGURE(..) +AC_PROG_CPP AM_CONDITIONAL(NEWLIB_NANO_MALLOC, test x$newlib_nano_malloc = xyes) |