public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/26183] GDB build fails with error: ‘class std::basic_string_view<char>’ has no member named ‘to_string’ Date: Mon, 29 Jun 2020 18:19:53 +0000 [thread overview] Message-ID: <bug-26183-4717-gMf3U6IZVC@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26183-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26183 --- Comment #2 from Tom Tromey <tromey at sourceware dot org> --- The problem was latent before my patch. I think the issue is that our string_view has to_string, but C++ officially does not. https://en.cppreference.com/w/cpp/string/basic_string_view The gdb one was copied from libstdc++; I don't know if this represents a local divergence (seems unlikely), or if upstream / the standard changed. Probably the solution is to change gdbsupport's string view to have a "gdb::to_string" free function, then use that instead. When using the real string view, this can simply use a string constructor. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-06-29 18:19 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-29 17:50 [Bug build/26183] New: " bergner at linux dot ibm.com 2020-06-29 17:51 ` [Bug build/26183] " bergner at linux dot ibm.com 2020-06-29 17:57 ` tuliom at ascii dot art.br 2020-06-29 18:04 ` bergner at linux dot ibm.com 2020-06-29 18:19 ` tromey at sourceware dot org [this message] 2020-06-29 18:28 ` bergner at linux dot ibm.com 2020-06-29 18:34 ` tromey at sourceware dot org 2020-06-29 18:35 ` tromey at sourceware dot org 2020-06-29 18:36 ` tromey at sourceware dot org 2020-06-29 18:50 ` simark at simark dot ca 2020-06-29 19:27 ` tromey at sourceware dot org 2020-06-30 13:55 ` cvs-commit at gcc dot gnu.org 2020-06-30 14:45 ` tromey at sourceware dot 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-26183-4717-gMf3U6IZVC@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).