public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/94681] filesystem::sysmlink_status using stat instead of lstat when --disable-libstdcxx-filesystem-ts
Date: Mon, 10 Aug 2020 12:22:33 +0000 [thread overview]
Message-ID: <bug-94681-4-kjsXdmm0QG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94681-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94681
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:90f7636bf8df50940e0f749af60a6b374a8f09b4
commit r11-2633-g90f7636bf8df50940e0f749af60a6b374a8f09b4
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Mon Aug 10 13:21:59 2020 +0100
libstdc++: Make C++17 ignore --disable-libstdcxx-filesystem-ts [PR 94681]
The configure switch should only affect the optional Filesystem TS, not
the std::filesystem features of C++17.
libstdc++-v3/ChangeLog:
PR libstdc++/94681
* acinclude.m4 (GLIBCXX_CHECK_FILESYSTEM_DEPS): Do not depend on
$enable_libstdcxx_filesystem_ts.
* configure: Regenerate.
next prev parent reply other threads:[~2020-08-10 12:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 8:41 [Bug libstdc++/94681] New: " valentin.david at codethink dot co.uk
2020-04-21 8:42 ` [Bug libstdc++/94681] " redi at gcc dot gnu.org
2020-04-21 8:55 ` redi at gcc dot gnu.org
2020-08-10 12:22 ` cvs-commit at gcc dot gnu.org [this message]
2020-08-10 12:25 ` redi at gcc dot gnu.org
2020-08-10 14:37 ` clyon at gcc dot gnu.org
2020-08-10 16:04 ` redi at gcc dot gnu.org
2020-08-10 18:12 ` cvs-commit at gcc dot gnu.org
2020-09-21 23:00 ` cvs-commit at gcc dot gnu.org
2020-09-21 23:00 ` cvs-commit at gcc dot gnu.org
2020-09-21 23:14 ` cvs-commit at gcc dot gnu.org
2020-09-21 23:14 ` cvs-commit at gcc dot gnu.org
2020-09-21 23:14 ` redi at gcc dot gnu.org
2020-09-21 23:14 ` redi at gcc dot gnu.org
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=bug-94681-4-kjsXdmm0QG@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).