Re: Dependence on config.status

[Andrew Cagney <ac131313 at cygnus dot com>]

Eli Zaretskii wrote:
> 
> > Eli Zaretskii wrote:
> > >
> > > > Well, if memory serves, if you re-ran configure in such a way that
> > > > tm.h started linking to a different file, then the config.status
> > > > dependency was the only way to force a rebuild.
> > >
> > > How about adding some #define to config.h that would also change when
> > > this happens?
> >
> > Such as the names of the tm, xm and nm files?
> 
> Yes, that's what I had in mind.  Since the configure scripts already
> knows the names of those files, it could put them into config.h.

Well I've long had in mind a ``maint build-info'' command that printed
out things like:

	tm/xm/hm.h
	the --host/target/build tupples
	the compiler
	the path to the source tree
	the build date
	the user/machine

Assuming your suggestion works (JimK doesn't find more technical flaws
(1) :-) A change putting tm/xm/hm into config.h is ok with me :-)

	Andrew

(1) I think changing tm/xm/nm happens sufficiently often for it to be
dangerous to not force a rebuild.