public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-6263] libcc1: Fix up libcc1 configure [PR98330]
Date: Fri, 18 Dec 2020 19:26:28 +0000 (GMT) [thread overview]
Message-ID: <20201218192629.0065F3857004@sourceware.org> (raw)
https://gcc.gnu.org/g:5dc998933e7aa737f4a45a8a2885d42d5288d51a
commit r11-6263-g5dc998933e7aa737f4a45a8a2885d42d5288d51a
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Dec 18 20:25:26 2020 +0100
libcc1: Fix up libcc1 configure [PR98330]
Either we should write test x$darwin_dynamic_lookup = xyes
or we should make sure the variable is always defined to non-empty string.
2020-12-18 Jakub Jelinek <jakub@redhat.com>
PR bootstrap/98380
* configure.ac: Set darwin_dynamic_lookup=no instead to empty
string.
* configure: Regenerated.
Diff:
---
libcc1/configure | 2 +-
libcc1/configure.ac | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/libcc1/configure b/libcc1/configure
index d3eedfec9b8..ac0f0312cc9 100755
--- a/libcc1/configure
+++ b/libcc1/configure
@@ -14976,7 +14976,7 @@ LIBS="$LIBS $libcc1_cv_lib_sockets"
case "$host" in
*-*-darwin*) darwin_dynamic_lookup=yes ;;
- *) darwin_dynamic_lookup= ;;
+ *) darwin_dynamic_lookup=no ;;
esac
if test $darwin_dynamic_lookup = yes; then
DARWIN_DYNAMIC_LOOKUP_TRUE=
diff --git a/libcc1/configure.ac b/libcc1/configure.ac
index 262e0a61e6f..648bcbae12a 100644
--- a/libcc1/configure.ac
+++ b/libcc1/configure.ac
@@ -106,7 +106,7 @@ LIBS="$LIBS $libcc1_cv_lib_sockets"
case "$host" in
*-*-darwin*) darwin_dynamic_lookup=yes ;;
- *) darwin_dynamic_lookup= ;;
+ *) darwin_dynamic_lookup=no ;;
esac
AM_CONDITIONAL(DARWIN_DYNAMIC_LOOKUP, test $darwin_dynamic_lookup = yes)
reply other threads:[~2020-12-18 19:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201218192629.0065F3857004@sourceware.org \
--to=jakub@gcc.gnu.org \
--cc=gcc-cvs@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).