Re: [autodeps] gnu-nat, autogenerated files

[Daniel Jacobowitz <drow@false.org>]

On Tue, Sep 09, 2008 at 10:03:13AM -0600, Tom Tromey wrote:
> >>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
> 
> Pedro> These are generated headers, built from the corresponding .defs files in
> Pedro> the tree.  Their build rules are in config/i386/i386gnu.mh.
> 
> Pedro> Is this the right approach?
> 
> Yes.
> 
> 
> I didn't know about the .mh files, sorry about that.  I read through
> them all just now and I noticed that they inconsistently use NAT_FILE.
> Some use config/ and some do not, e.g.:
> 
> config/pa/linux.mh:NAT_FILE= config/nm-linux.h
> config/alpha/alpha-osf3.mh:NAT_FILE= nm-osf3.h
> 
> AFAICT this variable is only used for the TAGS rule.  So, maybe it
> doesn't matter much.  Or maybe it could just be deleted.

No, search for NAT_FILE in configure.ac.  This file is included as
nm.h in native GDBs; it's where native target configuration used to
live, and the remaining ones are still used.

Also:

    case "${nativefile}" in
      nm-*.h ) GDB_NM_FILE="config/${gdb_host_cpu}/${nativefile}" ;;
      * ) GDB_NM_FILE="${nativefile}"
    esac

-- 
Daniel Jacobowitz
CodeSourcery