Re: [patch] for mig check in GDB's configure

[Yue Lu <hacklu.newborn@gmail.com>]

Hi,

On Sun, May 5, 2013 at 1:22 AM, Doug Evans <dje@google.com> wrote:
> On Fri, May 3, 2013 at 3:43 AM, 陆岳 <hacklu.newborn@gmail.com> wrote:
>>> Hmm, I think that instead of only examining the host system, $host, this
>>> also needs to examine the target system, $target.  (Please tell if the
>>> difference between build, host, and target system is not clear to you.)
>>> The MIG tool is used to generate files (from RPC definition files) that
>>> are used by the native GDB port for GNU Hurd (which, of couse, is the
>>> only GNU Hurd port that currently exists.)  But if someone, for example,
>>> builds GDB targeting mips-linux-gnu on a GNU Hurd system, they would not
>>> need the MIG tool.
>>>
> I can run gdb on an x86 system and debug a program running on a mips
> system via gdbserver (or some other program that speaks gdb's remote
> protocol).
>
> --build = system you're building the tool on
> --host = system the tool will run on
> --target = system the tool will handle or target (generate code for in
> the case of gcc, debug in the case of gdb)
>
> [These terms are common to all GNU tools, not just gcc btw.]

Thanks for the explanation. I have known about these three terms.

> So for example I *could*, given appropriately ported tools,
> build gdb on x86, run it on mips, and have it debug programs running on arm.

But I have one more question, why the one run on GNU Hurd which
targeting arm doesn't need to use MIG? As it run under GNU Hurd, it
must use the message transport facility and need to use MIG to
generate the interface file automatically or someone  write it by
hands.

-- 
Yue Lu (陆岳)