From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++ <libstdc++@gcc.gnu.org>, redi@gcc.gnu.org
Subject: [PATCH] libstdc++: fix typo in acinclude.m4.
Date: Thu, 27 Jan 2022 14:48:58 +0100 [thread overview]
Message-ID: <c68f88ec-7046-bb58-38d1-3e0a60db07be@suse.cz> (raw)
Hi.
May I install an obvious typo that causes build error (described in the PR).
Ready to be installed?
Thanks,
Martin
PR libstdc++/104259
libstdc++-v3/ChangeLog:
* acinclude.m4: Fix typo.
* configure: Regenerate.
---
libstdc++-v3/acinclude.m4 | 2 +-
libstdc++-v3/configure | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/libstdc++-v3/acinclude.m4 b/libstdc++-v3/acinclude.m4
index 7b6b807114a..a93252076b9 100644
--- a/libstdc++-v3/acinclude.m4
+++ b/libstdc++-v3/acinclude.m4
@@ -4744,7 +4744,7 @@ dnl
[glibcxx_cv_fdopendir=yes],
[glibcxx_cv_fdopendir=no])
])
- if test $glibcxx_cv_truncate = yes; then
+ if test $glibcxx_cv_fdopendir = yes; then
AC_DEFINE(HAVE_FDOPENDIR, 1, [Define if fdopendir is available in <dirent.h>.])
fi
dnl
diff --git a/libstdc++-v3/configure b/libstdc++-v3/configure
index 5c6e51f5c11..2b2f85782b1 100755
--- a/libstdc++-v3/configure
+++ b/libstdc++-v3/configure
@@ -77080,7 +77080,7 @@ fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $glibcxx_cv_fdopendir" >&5
$as_echo "$glibcxx_cv_fdopendir" >&6; }
- if test $glibcxx_cv_truncate = yes; then
+ if test $glibcxx_cv_fdopendir = yes; then
$as_echo "#define HAVE_FDOPENDIR 1" >>confdefs.h
--
2.34.1
next reply other threads:[~2022-01-27 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 13:48 Martin Liška [this message]
2022-01-27 14:25 ` Jonathan Wakely
2022-01-27 14:35 ` Martin Liška
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=c68f88ec-7046-bb58-38d1-3e0a60db07be@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=redi@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).