Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: PREPARE_TO_PROCEED; Was: More multi-arch and cleanups for m68k-linux
Date: Mon, 26 May 2003 22:37:00 -0000	[thread overview]
Message-ID: <m3brxp49pm.fsf@whitebox.local> (raw)
In-Reply-To: <20030526195215.GA10404@nevyn.them.org>

Daniel Jacobowitz <drow@mvista.com> writes:

> But what does the definition of PREPARE_TO_PROCEED in config/nm-linux.h
> have to do with multi-arching m68k now?

The problem is that in multi-arch level 2 gdbarch.h complains about
the non-multi-arch definition of the macro in a native configuration.

Andreas.


      reply	other threads:[~2003-05-26 22:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-25 18:51 Andreas Schwab
2003-05-26 19:41 ` PREPARE_TO_PROCEED; Was: " Andrew Cagney
2003-05-26 19:57   ` Daniel Jacobowitz
2003-05-26 22:37     ` Andreas Schwab [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=m3brxp49pm.fsf@whitebox.local \
    --to=schwab@suse.de \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.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