From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: "H . J . Lu" <hjl@lucon.org>, GDB <gdb@sourceware.cygnus.com>,
gdb-patches@sourceware.cygnus.com
Subject: Re: How to configure a cross gdb to debug natively
Date: Fri, 13 Jul 2001 15:15:00 -0000 [thread overview]
Message-ID: <3B4F730E.5000904@cygnus.com> (raw)
In-Reply-To: <20010713140826.A19730@nevyn.them.org>
> On Fri, Jul 13, 2001 at 01:48:06PM -0700, H . J . Lu wrote:
>
>> On Fri, Jul 13, 2001 at 01:23:46PM -0700, H . J . Lu wrote:
>
>> > I'd like to configure gdb inside a tree with binutils, gcc and gdb
>> > on Linux/i686 with
>> >
>> > # ../configure --target=i386-linux ....
>> >
>> > I do that on purpose so that gcc and binutils won't use any files
>> > on the host machine. But gdb refuses to debug natively on Linux/i686
>> > since it is configured as a cross gdb, However, Linux/i686 is
>> > compatible with i386-linux, how can I convince gdb to debug natively?
>> >
> I don't think this is generally appropriate. For one thing, it further
> breaks the consistency of cross-compiling. If I have ${host} !=
> ${target} then I am definitely building a cross debugger and that's
> what I expect to get out. Why not build your tools --host=i386-linux
> instead?
Yes.
H.J., you need to canadian cross GDB using the cross-GCC and
cross-BINUTILS you just built.
Andrew
prev parent reply other threads:[~2001-07-13 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 13:23 H . J . Lu
2001-07-13 13:48 ` H . J . Lu
2001-07-13 14:06 ` Alexandre Oliva
2001-07-13 14:08 ` Daniel Jacobowitz
2001-07-13 14:12 ` H . J . Lu
2001-07-13 14:28 ` Daniel Jacobowitz
2001-07-13 14:45 ` H . J . Lu
2001-07-13 14:52 ` Daniel Jacobowitz
2001-07-13 15:15 ` Andrew Cagney [this message]
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=3B4F730E.5000904@cygnus.com \
--to=ac131313@cygnus.com \
--cc=dmj+@andrew.cmu.edu \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=hjl@lucon.org \
/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