Re: toplevel Makefile.in: generate with autogen

[Alexandre Oliva <aoliva@redhat.com>]

On Sep 21, 2002, Nathanael Nerode <neroden@doctormoo.dyndns.org> wrote:

> This change causes toplevel Makefile.in to be generated by autogen from
> Makefile.tpl and Makefile.def; consensus was reached a while back that
> this was a reasonable thing to do.

Hmm...  I thought this would also move into Makefile.def the
dependencies of each module (configure, build and perhaps install
dependencies).  I think this would be a nice improvement in the
future, since the information would all be collected in a single
place.

Also, I've noticed that parallel make recently hasn't been as
efficient as it was in the past as to processing multiple directories
simultaneously.  It appears that these days it only processes
directories sequentially, even though they're not using as many
processes as specified for the top-level make -j.  I thought this
might have been caused by changes in make itself, but last week I've
been working with parallel makes on an old branch and I found out it
was not the case: it's actually something that changed in the GCC
build infrastructure.  Could I perhaps convince you to have a look?
:-)

I'd approve this patch (with the same caveats) if it had a ChangeLog
entry and it accompanied documentation changes that introduced the
dependency on autogen and explained how to rebuild Makefile.in from
its new dependencies.  A new rule to that end in Makefile.in would
definitely be welcome.  config/gcc_update should also be adjusted.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer