From: Johannes Stezenbach <js@convergence.de>
To: Lanny DeVaney <ldevaney@redhat.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: gdbserver
Date: Tue, 12 Mar 2002 21:45:18 +0100 [thread overview]
Message-ID: <20020312204518.GA8593@convergence.de> (raw)
In-Reply-To: <3C8E5560.2090907@redhat.com>
On Tue, Mar 12, 2002 at 01:22:08PM -0600, Lanny DeVaney wrote:
> I've looked back through the archives and find some references to
> problems configuring and/or building gdbserver for mips-linux.
>
> I'm attempting to build gdb/gdbserver with --target=mips-linux as well,
> using gdb-5.1.1. Have the earlier issues (they looked to be 1-2 years
> old) been resolved or am I still looking at a "manual build" process?
> I'm getting lots of errors with the build, although the configure seems
> to go OK. x86 host, linux-mips target.
I tried the gdb+dejagnu-20020305 snapshot recently and
both gdb and gdbserver built without problems. IIRC
gdbserver was still broken in gdb-5.1.1.
I haven't used the newly built gdbserver yet, though.
Regards,
Johannes
next prev parent reply other threads:[~2002-03-12 21:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 19:22 gdbserver Lanny DeVaney
2002-03-12 20:45 ` Johannes Stezenbach [this message]
2002-03-12 21:46 ` gdbserver Lanny DeVaney
2002-03-12 22:10 ` gdbserver Daniel Jacobowitz
2002-03-12 22:16 ` gdbserver Lanny DeVaney
-- strict thread matches above, loose matches on Subject: below --
2007-06-26 15:20 [PATCH] generic clk API implementation for MIPS Franck Bui-Huu
2007-06-26 16:33 ` Atsushi Nemoto
2007-06-27 15:39 ` Christoph Hellwig
2007-06-28 2:22 ` Atsushi Nemoto
2007-06-28 8:37 ` Christoph Hellwig
2007-06-28 20:45 ` gdbserver Ratin Rahman (mratin)
2007-06-28 20:45 ` gdbserver Ratin Rahman (mratin)
2007-06-28 21:41 ` gdbserver David Daney
2007-06-28 22:19 ` gdbserver Ratin Rahman (mratin)
2007-06-28 22:19 ` gdbserver Ratin Rahman (mratin)
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=20020312204518.GA8593@convergence.de \
--to=js@convergence.de \
--cc=ldevaney@redhat.com \
--cc=linux-mips@oss.sgi.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