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
