public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus.boeck02 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/95392] New: Build failure on MinGW
Date: Thu, 28 May 2020 17:01:10 +0000 [thread overview]
Message-ID: <bug-95392-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95392
Bug ID: 95392
Summary: Build failure on MinGW
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: markus.boeck02 at gmail dot com
Target Milestone: ---
Current trunk version of GCC (tested with HEAD at
4833c1adc3c7b125bf1c59e8bd8d802ac3b0d205) fails to build using MinGW. The
compiler error is as follows:
In file included from
/mnt/c/GCC-Build/gcc/build/x86_64-w64-mingw32/libstdc++-v3/include/filesystem:45,
from ../../../../../libstdc++-v3/src/c++17/fs_ops.cc:32,
from ../../../../../libstdc++-v3/src/c++17/cow-fs_ops.cc:26:
/mnt/c/GCC-Build/gcc/build/x86_64-w64-mingw32/libstdc++-v3/include/bits/fs_path.h:
In function 'std::filesystem::path std::filesystem::u8path(const _Source&)':
/mnt/c/GCC-Build/gcc/build/x86_64-w64-mingw32/libstdc++-v3/include/bits/fs_path.h:789:32:
error: '_S_string_from_iter' is not a member of 'std::filesystem::path'
789 | std::string __s = path::_S_string_from_iter(__source);
|
The change that introduced the breakage is
584d52b088f9fcf78704b504c3f1f07e17c1cded. Reverting this commit makes the build
succeed
next reply other threads:[~2020-05-28 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 17:01 markus.boeck02 at gmail dot com [this message]
2020-05-28 17:37 ` [Bug libstdc++/95392] [11 Regression] " redi at gcc dot gnu.org
2020-05-28 17:38 ` redi at gcc dot gnu.org
2020-06-01 23:14 ` cvs-commit at gcc dot gnu.org
2020-06-01 23:15 ` 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-95392-4@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).