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

On Mon, May 26, 2003 at 03:40:06PM -0400, Andrew Cagney wrote:
> >The only thing that prevents m68k-linux from advancing to multi-arch
> >level 2 is the PREPARE_TO_PROCEED definition in config/nm-linux.h.
> >How can this be multi-arched given that this is a native-only thing?
> 
> I _think_ the current plan is along the lines of make 
> generic_prepare_proceed(?) the default, and leave HP/UX as the exception.
> 
> Does the generic version work on GNU/Linux?  (Hmm??? nothing appears to 
> currently use it!)

What timing!  This is almost to the top of my todo list to redo
again...

There were three targets using their own prepare to proceed, IIRC:
mach3, hppa OSF, and HP/UX.  Two of those are gone now.  I believe that
generic_prepare_to_proceed will not only work on GNU/Linux (it does),
but that it will also work on HP/UX.  I need to test this hypothesis.

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

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-05-26 19:57 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 [this message]
2003-05-26 22:37     ` Andreas Schwab

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=20030526195215.GA10404@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=schwab@suse.de \
    /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