From: "H . J . Lu" <hjl@lucon.org>
To: GDB <gdb@sourceware.cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: How to configure a cross gdb to debug natively
Date: Fri, 13 Jul 2001 13:48:00 -0000 [thread overview]
Message-ID: <20010713134806.A28554@lucon.org> (raw)
In-Reply-To: <20010713132346.A28020@lucon.org>
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?
>
This patch seems to do the trick for me.
H.J.
----
2001-07-13 H.J. Lu (hjl@gnu.org)
* configure.in: Check "${target_os}" = "${host_os}" and
"${gdb_target_cpu}" = "${gdb_host_cpu}" for native files
instead of "${target}" = "${host}".
* configure: Regenerated.
--- gdb/configure.in.arch Fri Jul 13 12:12:33 2001
+++ gdb/configure.in Fri Jul 13 13:36:15 2001
@@ -1183,7 +1183,7 @@ s/GDB_MULTI_ARCH[ ]*=[ ]*\([^ ]*\)[
# these really aren't orthogonal true/false values of the same condition,
# but shells are slow enough that I like to reuse the test conditions
# whenever possible
-if test "${target}" = "${host}"; then
+if test "${target_os}" = "${host_os}" -a "${gdb_target_cpu}" = "${gdb_host_cpu}"; then
nativefile=`sed -n '
s/NAT_FILE[ ]*=[ ]*\([^ ]*\)/\1/p
' ${host_makefile_frag}`
next parent reply other threads:[~2001-07-13 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010713132346.A28020@lucon.org>
2001-07-13 13:48 ` H . J . Lu [this message]
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 15:15 ` Andrew Cagney
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=20010713134806.A28554@lucon.org \
--to=hjl@lucon.org \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=gdb@sourceware.cygnus.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