Re: Makefile.global is kind of a pain

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> ... Instead of each
> Makefile including Makefile.global, each makefile is pasted together with
> a global makefile of sorts when it's created by config.status.

Hmm. My only objection to that is that it used to be possible to fix
some kinds of configure botches by hand-editing Makefile.global (which
after all is a configure output from Makefile.global.in). But now,
anything I don't like about what configure did is going to be physically
replicated in umpteen files, so if I don't understand autoconf well
enough to make configure do exactly what I wanted, I'm pretty much up
the creek.

What's so wrong with including Makefile.global? Maybe the system
won't know that an edit there requires a global rebuild, but I'd
rather have to do a "make clean"/"make all" after changing
Makefile.global than manually edit dozens upon dozens of makefiles
to get the same result.

Awhile back I was complaining that configure was dumping its results
into too many files already. This sounds like it will make that problem
many times worse.

regards, tom lane