From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: unlvsur unlvsur <unlvsur@live.com>
Cc: "unlvsur unlvsur via Libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: ENOTSUP macro does not exist on DJGPP CRT
Date: Mon, 1 Mar 2021 16:53:23 +0000 [thread overview]
Message-ID: <CAH6eHdRMGNJGjvVoba7uz64nvkFRT8B_WAWun7CZ5U99USnxRA@mail.gmail.com> (raw)
In-Reply-To: <DM6PR05MB4697EAEA78E3D8EE55716462D69C9@DM6PR05MB4697.namprd05.prod.outlook.com>
On Sat, 27 Feb 2021 at 19:49, unlvsur unlvsur via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> This is the errno.h on djgpp.
>
> In file included from ../../../../../gcc/libstdc++-v3/src/c++17/cow-fs_ops.cc:26:
> ../../../../../gcc/libstdc++-v3/src/c++17/fs_ops.cc: In function 'void std::filesystem::copy(const std::filesystem::path&, const std::filesystem::path&, std::filesystem::copy_options, std::error_code&)':
> ../../../../../gcc/libstdc++-v3/src/c++17/fs_ops.cc:363:44: error: 'not_supported' is not a member of 'std::errc'
> 363 | ec = std::make_error_code(std::errc::not_supported);
> | ^~~~~~~~~~~~~
Please report it to bugzilla.
prev parent reply other threads:[~2021-03-01 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 19:22 unlvsur unlvsur
2021-03-01 16:53 ` Jonathan Wakely [this message]
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=CAH6eHdRMGNJGjvVoba7uz64nvkFRT8B_WAWun7CZ5U99USnxRA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=libstdc++@gcc.gnu.org \
--cc=unlvsur@live.com \
/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).