From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com, mrg@redhat.com
Subject: Re: [patch/rfc] Don't assume the host
Date: Sun, 20 Jan 2002 09:13:00 -0000 [thread overview]
Message-ID: <3C4AFA9D.6050603@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020120102829.8679O@is>
> On Fri, 18 Jan 2002, Andrew Cagney wrote:
>
>
>> this time it includes updates to gdbint.texinfo (Eli?).
>
>
> Approved.
>
>
>> One thing I noticed in tweeking the doco is that there is a mysterious
>> but almost useless chapter ``Porting GDB''. The information that
>> chapter provides is also present elsewhere in a more complete form.
>
>
> What is that other chapter?
Much of ``Porting GDB'' also appears in ``Host Definition''. The two
could do with some rationalization.
>> + New host only configurations do not need this file.
>
>
> What is a ``host only configuration''? Is it an a.k.a. for
> ``native''? I'm not sure, since you later say
I suspect strictly speaking I've used the correct technical word but the
usage isn't exactly mainstream.
host - the machine GDB will run on
build - the machine your compiling GDB on
target - the machine that GDB will debug
Native is a special case where host==target.
Cross is where host!=target
Adding to the problems is (as I've now documented) the way GDB uses HOST
when it probably means NATIVE! This one really messes up people playing
with GDBSERVER.
>> ! New host and native configurations do not need this file.
>
>
> Otherwise, I have no comments.
Thanks!
Andrew
next prev parent reply other threads:[~2002-01-20 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 20:44 Andrew Cagney
2002-01-18 13:56 ` Andrew Cagney
2002-01-20 0:29 ` Eli Zaretskii
2002-01-20 9:13 ` Andrew Cagney [this message]
2002-01-20 10:21 ` Andrew Cagney
2002-01-20 10:25 ` Eli Zaretskii
2002-01-20 10:38 ` Andrew Cagney
2002-01-20 10:55 ` Eli Zaretskii
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=3C4AFA9D.6050603@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=mrg@redhat.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