This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: How to configure a cross gdb to debug natively
- To: Daniel Jacobowitz <dmj+ at andrew dot cmu dot edu>
- Subject: Re: How to configure a cross gdb to debug natively
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Fri, 13 Jul 2001 18:15:42 -0400
- Cc: "H . J . Lu" <hjl at lucon dot org>, GDB <gdb at sourceware dot cygnus dot com>,gdb-patches at sourceware dot cygnus dot com
- References: <20010713132346.A28020@lucon.org> <20010713134806.A28554@lucon.org> <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