Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Eliminate deprecated_tm_print_insn
Date: Thu, 04 Sep 2003 19:27:00 -0000	[thread overview]
Message-ID: <20030904192723.GL1859@cygbert.vinschen.de> (raw)
In-Reply-To: <3F5781C1.8030003@redhat.com>

On Thu, Sep 04, 2003 at 02:17:37PM -0400, Andrew Cagney wrote:
> >On Thu, Aug 28, 2003 at 06:35:43PM -0400, Andrew Cagney wrote:
> >
> >>2003-08-28  Andrew Cagney  <cagney@redhat.com>
> >>
> >>	* arch-utils.h (legacy_print_insn): Delete declaration.
> >>	* arch-utils.c (legacy_print_insn): Delete function.
> >>	* disasm.c (deprecated_tm_print_insn_info): Delete.
> >>	(_initialize_disasm): Delete function, contained code initializing
> >>	deprecated_tm_print_insn_info.
> >>	* gdbarch.sh (deprecated_tm_print_insn): Delete.
> >>	(deprecated_tm_print_insn_info): Delete.
> >>	(TARGET_PRINT_INSN): Do not provide a default.
> >>	* gdbarch.h, gdbarch.c: Re-generate.
> >
> >
> >After this change I'm getting an error when building:
> >
> >gcc -g       \
> >        -o gdb gdb.o main.o cli-dump.o cli-decode.o cli-script.o 
> >        cli-cmds.o cli-setshow.o cli-utils.o cli-logging.o cli-interp.o 
> >        mi-out.o mi-console.o mi-cmds.o mi-cmd-env.o mi-cmd-var.o 
> >        mi-cmd-break.o mi-cmd-stack.o mi-cmd-file.o mi-cmd-disas.o 
> >        mi-symbol-cmds.o mi-interp.o mi-main.o mi-parse.o mi-getopt.o 
> >        libgdb.a \
> >	          
> Check that your opcodes directory is up-to-date.  In particular it 
> contains dis-init.o.

Uh, thanks, that did it.

Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.


      reply	other threads:[~2003-09-04 19:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 22:35 Andrew Cagney
2003-09-03 23:50 ` Andrew Cagney
2003-09-04 18:05 ` Corinna Vinschen
2003-09-04 18:17   ` Andrew Cagney
2003-09-04 19:27     ` Corinna Vinschen [this message]

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=20030904192723.GL1859@cygbert.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=gdb-patches@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