public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "martin at lispworks dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/31918] New: Error: no template named 'unordered_map' when compiling on FreeBSD 13.2
Date: Fri, 21 Jun 2024 14:49:03 +0000	[thread overview]
Message-ID: <bug-31918-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31918
           Summary: Error: no template named 'unordered_map' when
                    compiling on FreeBSD 13.2
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: martin at lispworks dot com
  Target Milestone: ---

Created attachment 15590
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15590&action=edit
Patch to include unordered_map header

Compiling on FreeBSD 13.2 with the default clang version 14.0.5 and top level
configure options --with-python=/usr/local/bin/python3.9 gives this error:

  CXX    ada-exp.o
../../binutils-gdb/gdb/ada-exp.y:100:8: error: no template named
'unordered_map' in namespace 'std'
  std::unordered_map<std::string, std::vector<ada_index_var_operation *>>
  ~~~~~^
1 error generated.

The attached patch fixes it.

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

             reply	other threads:[~2024-06-21 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 14:49 martin at lispworks dot com [this message]
2024-06-22 20:02 ` [Bug build/31918] " tromey at sourceware dot org
2024-06-24 12:23 ` cvs-commit at gcc dot gnu.org
2024-06-24 12:26 ` cvs-commit at gcc dot gnu.org
2024-06-24 12:26 ` 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-31918-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).