Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: host_makefile_frag and cross debugging
Date: Fri, 24 Jun 2005 14:33:00 -0000	[thread overview]
Message-ID: <op.ssvpbaxco669wz@terrorhawk.bri.st.com> (raw)
In-Reply-To: <20050624140917.GA16942@nevyn.them.org>

On Fri, 24 Jun 2005 15:09:17 +0100, Daniel Jacobowitz <drow@false.org>  
wrote:
> Host fragments are for native debugger support routines now - only.

So what's the official way of making host configurations these days then?

>> What am I missing?
>
> You're missing the fact that xm-mingw32.h comes from your local
> patches, not from the FSF tree.  CVS gdb has absolutely no xm files
> left - even after Mark has added most of a MinGW host support.

That may be true - I haven't checked - but GDB 6.3 still had two:

   $ find . -name 'xm-*.h'
   ./gdb/config/i386/xm-cygwin.h
   ./gdb/config/i386/xm-go32.h

and these do exactly the sort of things I need done. The MinGW patches  
have merely followed the pattern.

I don't deny that I may need to do it a different way, but somehow I need  
to make the adjustments required by Windows, even though the debugger is  
targeted at SH. Any pointers would be great.

Thanks

Andrew Stubbs


  reply	other threads:[~2005-06-24 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 11:46 Andrew STUBBS
2005-06-24 14:09 ` Daniel Jacobowitz
2005-06-24 14:33   ` Andrew STUBBS [this message]
2005-06-24 14:37     ` Daniel Jacobowitz
2005-06-24 14:52       ` Andrew STUBBS
2005-06-24 18:56         ` Eli Zaretskii

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=op.ssvpbaxco669wz@terrorhawk.bri.st.com \
    --to=andrew.stubbs@st.com \
    --cc=drow@false.org \
    --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