From: Anthony Green <green@redhat.com>
To: cagney@redhat.com
Cc: gdb@sources.redhat.com
Subject: gdb build failure
Date: Fri, 05 Sep 2003 01:48:00 -0000 [thread overview]
Message-ID: <1062701302.29091.46.camel@escape> (raw)
Hi Andrew -
This patch...
http://sources.redhat.com/ml/gdb-patches/2003-09/msg00033.html
...breaks the gdb build, since gdbtk-cmds.c still references one of the
deprecated functions you deleted (deprecated_tm_print_insn_info).
AG
--
Anthony Green <green@redhat.com>
Red Hat, Inc.
reply other threads:[~2003-09-05 1:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1062701302.29091.46.camel@escape \
--to=green@redhat.com \
--cc=cagney@redhat.com \
--cc=gdb@sources.redhat.com \
/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