Re: host_makefile_frag and cross debugging

[Daniel Jacobowitz <drow@false.org>]

On Fri, Jun 24, 2005 at 12:44:46PM +0100, Andrew STUBBS wrote:
> I have traced the problem to the gdb/configure.in:
> 
>   frags=
>    if test "${target}" = "${host}"; then
>      host_makefile_frag=${srcdir}/config/${gdb_host_cpu}/${gdb_host}.mh
>      if test ! -f ${host_makefile_frag}; then
>        AC_MSG_ERROR("*** Gdb does not support native target ${host}")
>      fi
>      frags="$frags $host_makefile_frag"
>    else
>      host_makefile_frag=/dev/null
>    fi
> 
> Why does it test if host and target are the same? Surely the whole point  
> of having separate files is that you can mix and match?

Host fragments are for native debugger support routines now - only.

> I find that this was done in CVS configure.in version 1.175 in which the  
> following comment was actually removed:
> 
>      # When building a native debuger the .mh file containing things	  
>      # like NATDEPFILES is needed.  Cross debuggers don't need .mh	  
>      # since it no longer contains anything useful.
> 
> Apparently, in this case it does contain something useful - it configures  
> the xm-mingw32.h file which configures the correct separator.
> 
> What am I missing?

You're missing the fact that xm-mingw32.h comes from your local
patches, not from the FSF tree.  CVS gdb has absolutely no xm files
left - even after Mark has added most of a MinGW host support.

-- 
Daniel Jacobowitz
CodeSourcery, LLC