From: "H . J . Lu" <hjl@lucon.org>
To: "Steven J. Hill" <sjhill@cotw.com>
Cc: binutils@sources.redhat.com, gdb@sourceware.cygnus.com,
linux-mips@oss.sgi.com
Subject: Re: Continued MIPS kernel debugging symbols problem...
Date: Fri, 14 Sep 2001 08:07:00 -0000 [thread overview]
Message-ID: <20010914080712.A13976@lucon.org> (raw)
In-Reply-To: <3BA16CAA.6B4DF4A1@cotw.com>
On Thu, Sep 13, 2001 at 09:34:18PM -0500, Steven J. Hill wrote:
> I did read them a few times and it appears that all the
> necessary changes are in the current gdb and insight CVS
> repositories. I checked out the latest sources a half
> hour ago and compiled both gdb and insight using the
> configuration line:
>
> configure --prefix=/opt/tools --target=mipsel-linux-elf
^^^^^^^^^^^^^^^
I don't know if it will configure anything for Linux/mips. I use
mipsel-linux.
H.J.
next prev parent reply other threads:[~2001-09-14 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 19:43 Steven J. Hill
2001-09-13 21:28 ` Daniel Jacobowitz
2001-09-14 8:07 ` H . J . Lu [this message]
2001-09-20 5:21 ` Amit S. Kale
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=20010914080712.A13976@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=gdb@sourceware.cygnus.com \
--cc=linux-mips@oss.sgi.com \
--cc=sjhill@cotw.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