apachen Makefile no longer a dependency?

[Rodent of Unusual Size <co...@decus.org>]

    Previously, if you ran Configure, it created a new Makefile which
    contained a reflexive dependency: any time the Makefile was touched,
    it forced a complete recompile (everything was dependent upon the
    Makefile).

    The new Configure/Makefile in apachen doesn't do this any more.  I
    re-ran Configure, then Make, and it only compiled stuff in my
    modules/* directories (*not* modules/standard) and modules.c.  The
    former is because my personal module Makefiles (including the one in
    modules/example, btw) include the src/Makefile dependency.

    Is this a goodness?  I don't think so; what if the EXTRA_CFLAGS
    definition is changed?  Nothing will get recompiled.

    Looking at the generated Makefile, $(OBJS) is dependent upon the
    Makefile, so I'm not sure why this would be happening.  Unless the
    default make on my system is so lame that it can't handle the fact
    that OBJS includes $(MODULES), and walks the dependency graph before
    second-level macro expansion.. can anyone confirm that this happens
    on their system?

    I think this should go back to the previous behaviour of everything
    being reliably dependent upon src/Makefile.  Other opinions?

    Oh, BTW: It looks like modules/last-built is only directly dependent
    upon modules *other* than those in modules/standard.  All of the
    modules/standard targets have *it* as a dependency, though.  It works,
    but seems slightly counter-intuitive.  Maybe this target could be
    renamed to something like "modules/nonstandard-last-built", and the
    dependency taken off the generated lines for files in
    modules/standard and just left on the httpd target?

    #ken    :-)}