Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] gdbserver overhaul
Date: Sun, 14 Oct 2001 18:44:00 -0000	[thread overview]
Message-ID: <20011014214419.A7881@nevyn.them.org> (raw)
In-Reply-To: <3BCA382D.30809@cygnus.com>

On Sun, Oct 14, 2001 at 09:13:17PM -0400, Andrew Cagney wrote:
> >I've added preprocessor gunk to make this compile on other non-Linux
> >gdbserver targets, since I only had the Linux ones available to test on.  I
> >tested on Linux/{ARM,i386,mips,ppc,sh}; the SH bits require some patches
> >available from the SH community but not yet in mainstream GDB, but I'm
> >including the gdbserver parts anyway.  I'm fairly sure that ia64 and m68k
> >will continue to work if they did beforehand.  Note that the "compile" at 
> >the
> >beginning of this paragraph is really "compile iff it already did".  I 
> >tried
> >to find a non-Linux target to test; I tried mips64vr5000-unknown-elf
> >(low-sim.c) and sparc-sun-solaris2.8 (low-solaris.c).  Neither built.  
> 
> I'm confused. What exacactly did you try here - what was the configure 
> and CC?

More accurately, neither built gdbserver.

I didn't set CC to anything special.  Because mips64vr5000-unknown-elf
is a simulator target, the cross-debugger build includes gdbserver.  It
didn't link, because MIPS has been multi-arched, and gdb_arch stuff is
scattered all over the headers.  For solaris, I got lots of
prototype-related errors trying to build in the gdbserver directory; I
don't remember offhand what they were.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2001-10-14 18:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11 13:15 Daniel Jacobowitz
2001-10-14 18:13 ` Andrew Cagney
2001-10-14 18:44   ` Daniel Jacobowitz [this message]
2001-10-16 21:12     ` Andrew Cagney
2001-10-16 21:24       ` Daniel Jacobowitz
2001-10-16 21:09 ` Andrew Cagney
2001-10-16 21:23   ` Daniel Jacobowitz
2001-10-17  4:45     ` Eli Zaretskii
2001-10-17  9:06     ` Andrew Cagney
2001-10-17 10:57       ` Daniel Jacobowitz
2001-10-17 12:34     ` gdbserver/{<foo>,<os>,<bar>}.c?; Was: " Andrew Cagney
2001-10-17 13:39       ` Daniel Jacobowitz
2002-09-27 15:35         ` Andrew Cagney
2002-09-27 15:49           ` Andrew Cagney
2001-10-18  1:11       ` Eli Zaretskii
2001-10-18  9:30         ` Andrew Cagney
2001-10-18 12:36           ` Eli Zaretskii
2001-10-18 11:59             ` Andrew Cagney
2001-10-18 12:08               ` Daniel Jacobowitz
2001-10-21  4:02       ` Mark Kettenis
2001-10-21  9:15         ` Andrew Cagney
2001-10-17 15:17   ` Daniel Jacobowitz
2001-10-18 14:28     ` Andrew Cagney
2001-10-18 17:06       ` Daniel Jacobowitz

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=20011014214419.A7881@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.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