From: hbusch@bnv-bamberg.de
To: gcc-help@gcc.gnu.org
Subject: Re: g++ version 7.5.0 and library <memory_resource>
Date: Mon, 08 Jun 2020 06:42:44 +0200 [thread overview]
Message-ID: <20200608064244.Horde.oyKLkkNT3lFysQLTt_gU5hh@webmail.bnv-bamberg.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2006072117500.31072@stedding.saclay.inria.fr>
Thanks a lot Marc for your quick help.
Even <experimental/memory_resource> did not help.
Here ...
https://gcc.gnu.org/onlinedocs/gcc-7.5.0/libstdc++/manual/manual/status.html#status.iso.2017
... I see that 7.5.0 does not include memory_resource.
Best regards
Harald
Quoting Marc Glisse <marc.glisse@inria.fr>:
> On Sun, 7 Jun 2020, 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
>>
>> Even adding -std=gnu++17 throws the same error.
>>
>> Can anybody please shed some light on this ?
>
> Try <experimental/memory_resource>
>
> --
> Marc Glisse
next prev parent reply other threads:[~2020-06-08 4:42 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 [this message]
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
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=20200608064244.Horde.oyKLkkNT3lFysQLTt_gU5hh@webmail.bnv-bamberg.de \
--to=hbusch@bnv-bamberg.de \
--cc=gcc-help@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).