public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "euloanty at live dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29019] New: build error: 'gdb_print' was not declared in this scope; did you mean 'gdb_printf'?
Date: Sun, 03 Apr 2022 02:22:32 +0000	[thread overview]
Message-ID: <bug-29019-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29019
           Summary: build error: 'gdb_print' was not declared in this
                    scope; did you mean 'gdb_printf'?
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: euloanty at live dot com
  Target Milestone: ---

../../../../../binutils-gdb/gdb/top.c: In function 'void
print_gdb_configuration(ui_file*)':
../../../../../binutils-gdb/gdb/top.c:1632:3: error: 'gdb_print' was not
declared in this scope; did you mean 'gdb_printf'?
 1632 |   gdb_print (stream, _("\
      |   ^~~~~~~~~
      |   gdb_printf
  CXX    unittests/cli-utils-selftests.o
make: *** [Makefile:1655: top.o] Error 1
make: *** Waiting for unfinished jobs....

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

             reply	other threads:[~2022-04-03  2:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03  2:22 euloanty at live dot com [this message]
2022-04-03  2:22 ` [Bug build/29019] " euloanty at live dot com
2022-04-03  2:23 ` euloanty at live dot com
2022-04-03 13:56 ` simark at simark dot ca

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-29019-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).