On Wednesday 10 September 2008 19:00:18, Joel Brobecker wrote:
> > 2008-09-09  Pedro Alves  <pedro@codesourcery.com>
> >
> > 	* Makefile.in (generated_files): Add $(host_generated_files).
> > 	* config/i386/i386gnu.mh (host_generated_files): New.
>
> This one is a little beyond my knowledge of Makefile, particularly
> since the build system has changed recently. The idea seems right to me
> (adding a new variable in the mh file). But I'm still wondering whether
> it would be possible to use the NAT_FILE to include the list of generated
> files. Tom, what do you think? Probably be a little hacky...

I think it would be hacky.  We want this list for a specific purpose: 
These are autogenerated files, that need to be generated before compiling
the NATDEPFILES.

> If we introduce a new variable, I propose that its name be capitalized,
> like most (if not all) variables we have been using so far. I like
> HOST_GENERATED_FILES as you suggested.
>

Hmmmm, looking at the docs you pointed below, I believe NAT_GENERATED_FILES
is more correct.  These files shouldn't be generated when building a cross
debugger hosted on the hurd.  I've made that change, hope it's OK.

> We also need to document this new variable in gdbint. Perhaps around
> there:
>
>     @table @file
>     @vindex NATDEPFILES
>     @item gdb/config/@var{arch}/@var{xyz}.mh
>     Specifies Makefile fragments needed by a @emph{native} configuration on
>     machine @var{xyz}.  In particular, this lists the required
>     native-dependent object files, by defining @samp{NATDEPFILES=@dots{}}.
>     Also specifies the header file which describes native support on
>     @var{xyz}, by defining @samp{NAT_FILE= nm-@var{xyz}.h}.  You can also
>     define @samp{NAT_CFLAGS}, @samp{NAT_ADD_FILES}, @samp{NAT_CLIBS},
>     @samp{NAT_CDEPS}, etc.; see @file{Makefile.in}.
>
>     @emph{Maintainer's note: The @file{.mh} suffix is because this file
>     originally contained @file{Makefile} fragments for hosting @value{GDBN}
>     on machine @var{xyz}.  While the file is no longer used for this
>     purpose, the @file{.mh} suffix remains.  Perhaps someone will
>     eventually rename these fragments so that they have a @file{.mn}
>     suffix.}
>

Hmmm, errmmm, I don't know what to do here.  :-)  The logical place
would be to add the new variable to the "You can also define" list, as
in the patch below, and possibly describe each of those
variables... but, looking closer, I don't see any variable of the "You
can also define" list being in use currently.  Looks like an
oportunity for further Makefile.in cleanup --- TM_CLIBS and TM_CDEPS
also looks like looking for garbage collection.

What do you think?

-- 
Pedro Alves