public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at linux dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/26183] New: GDB build fails with error: ‘class std::basic_string_view<char>’ has no member named ‘to_string’
Date: Mon, 29 Jun 2020 17:50:50 +0000	[thread overview]
Message-ID: <bug-26183-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26183

            Bug ID: 26183
           Summary: GDB build fails with error: ‘class
                    std::basic_string_view<char>’ has no member named
                    ‘to_string’
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: bergner at linux dot ibm.com
  Target Milestone: ---

Building current gdb trunk source using a gcc trunk build from today, I'm
seeing the following build (powerpc64le-linux) error:

/home/bergner/binutils/binutils-gdb/gdb/ada-lang.c: In constructor
‘ada_lookup_name_info::ada_lookup_name_info(const lookup_name_info&)’:
/home/bergner/binutils/binutils-gdb/gdb/ada-lang.c:13556:50: error: ‘class
std::basic_string_view<char>’ has no member named ‘to_string’
13556 |    = user_name.substr (1, user_name.size () - 2).to_string ();
      |                                                  ^~~~~~~~~
/home/bergner/binutils/binutils-gdb/gdb/ada-lang.c:13559:50: error: ‘class
std::basic_string_view<char>’ has no member named ‘to_string’
13559 |    = user_name.substr (1, user_name.size () - 1).to_string ();
      |                                                  ^~~~~~~~~
/home/bergner/binutils/binutils-gdb/gdb/ada-lang.c:13578:33: error: ‘using
string_view = using string_view = class std::basic_string_view<char>’ {aka
‘class std::basic_string_view<char>’} has no member named ‘to_string’
13578 |      m_encoded_name = user_name.to_string ();
      |                                 ^~~~~~~~~
/home/bergner/binutils/binutils-gdb/gdb/ada-lang.c:13581:29: error: ‘using
string_view = using string_view = class std::basic_string_view<char>’ {aka
‘class std::basic_string_view<char>’} has no member named ‘to_string’
13581 |  m_encoded_name = user_name.to_string ();
      |                             ^~~~~~~~~
make: *** [Makefile:1610: ada-lang.o] Error 1

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-06-29 17:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 17:50 bergner at linux dot ibm.com [this message]
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
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@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: 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).