From: hbusch@bnv-bamberg.de
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: g++ version 7.5.0 and library <memory_resource>
Date: Mon, 08 Jun 2020 06:40:38 +0200 [thread overview]
Message-ID: <20200608064038.Horde.YUYY8m-2hytGvtMxOtODHFM@webmail.bnv-bamberg.de> (raw)
In-Reply-To: <CAH6eHdStSjWOVT7whkTH7Uw4URj+kwgRPvg0Q800C6nW8Gk0AQ@mail.gmail.com>
Thanks a lot Jonathan for your quick help.
You are right, 7.5.0 does not include memory_resource.
Best regards
Harald
Quoting Jonathan Wakely <jwakely.gcc@gmail.com>:
> On Sun, 7 Jun 2020 at 20:12, <hbusch@bnv-bamberg.de> wrote:
>>
>> Hi,
>> I am using g++ version 7.5.0 on Linux Mint 19 Tara:
>>
>> g++ (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
>>
>> When I try to compile a source file which uses the Standard library
>> header <memory_resource> I get the following error:
>>
>> main.cpp:7:10: fatal error: memory_resource: No such file or directory
>>
>> As to my knowledge g++ version 7.5.0 supports C++17 and library
>> <memory_resource> is included since C++17. At least, this page tells
>> me that it has to be there:
>>
>> https://gcc.gnu.org/onlinedocs/gcc-7.5.0/libstdc++/api/a01004_source.html
>
> No it doesn't, it tells you a different header is part of libstdc++ in
> the 7.5.0 release.
>
> As
> https://gcc.gnu.org/onlinedocs/gcc-7.5.0/libstdc++/manual/manual/status.html#status.iso.2017
> says, the <memory_resource> header is not supported in 7.5.0.
prev parent reply other threads:[~2020-06-08 4:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 19:10 hbusch
2020-06-07 19:18 ` Marc Glisse
2020-06-08 4:42 ` hbusch
2020-06-08 7:46 ` Jonathan Wakely
2020-06-08 11:44 ` hbusch
2020-06-08 14:34 ` Jonathan Wakely
2020-06-07 21:56 ` Jonathan Wakely
2020-06-08 4:40 ` hbusch [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=20200608064038.Horde.YUYY8m-2hytGvtMxOtODHFM@webmail.bnv-bamberg.de \
--to=hbusch@bnv-bamberg.de \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.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).