From: Pedro Alves <palves@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: 陆岳 <hacklu.newborn@gmail.com>,
bug-hurd@gnu.org, gdb-patches@sourceware.org
Subject: Re: [patch] for mig check in GDB's configure
Date: Fri, 03 May 2013 14:51:00 -0000 [thread overview]
Message-ID: <5183CEEC.5020501@redhat.com> (raw)
In-Reply-To: <8738u4sc19.fsf@kepler.schwinge.homeip.net>
On 05/03/2013 09:28 AM, Thomas Schwinge 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.
>
> GDB folks, would it make sense to use something like:
>
> case $gdb_native:$host in
> [...]
> yes:i[[3456]]86-*-gnu*)
> [error if MIG not found]
>
> ..., to check that both host and target are GNU Hurd?
Sure. Looking at config/i386/i386gnu.mh, NAT_GENERATED_FILES
in particular, I think gdb will want to run mig even on
cross gdbs hosted on GNU Hurd, though...
--
Pedro Alves
prev parent reply other threads:[~2013-05-03 14:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB8fV=gfGtguD28FGa-A5DZT8jqvEA1AoaK4dO=cHMQcCVvB-w@mail.gmail.com>
2013-05-03 8:28 ` Thomas Schwinge
2013-05-03 10:44 ` 陆岳
[not found] ` <87txmkxlu6.fsf@violet.siamics.net>
2013-05-04 8:29 ` Yue Lu
2013-05-16 21:55 ` Thomas Schwinge
2013-05-17 5:30 ` Joel Brobecker
2013-05-17 6:34 ` Yue Lu
2013-05-17 7:00 ` Thomas Schwinge
2013-05-17 7:07 ` Joel Brobecker
2013-05-04 17:22 ` Doug Evans
2013-05-05 5:31 ` Yue Lu
2013-05-05 17:35 ` Doug Evans
2013-05-16 22:10 ` Thomas Schwinge
2013-05-03 14:51 ` Pedro Alves [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=5183CEEC.5020501@redhat.com \
--to=palves@redhat.com \
--cc=bug-hurd@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hacklu.newborn@gmail.com \
--cc=thomas@codesourcery.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