public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-6895] libstdc++: fix typo in acinclude.m4. Date: Thu, 27 Jan 2022 14:34:48 +0000 (GMT) [thread overview] Message-ID: <20220127143448.82126394742E@sourceware.org> (raw) https://gcc.gnu.org/g:14f339894db6ca7fe4772d5528c726694d2517c4 commit r12-6895-g14f339894db6ca7fe4772d5528c726694d2517c4 Author: Martin Liska <mliska@suse.cz> Date: Thu Jan 27 14:47:23 2022 +0100 libstdc++: fix typo in acinclude.m4. PR libstdc++/104259 libstdc++-v3/ChangeLog: * acinclude.m4: Fix typo. * configure: Regenerate. Diff: --- 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
reply other threads:[~2022-01-27 14:34 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=20220127143448.82126394742E@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-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: linkBe 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).