This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: subdir/toplevel dependence (was Re: (toplevel)...)
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Nathanael Nerode <neroden at twcny dot rr dot com>
- Cc: gcc-patches at gcc dot gnu dot org, gdb-patches at sources dot redhat dot com, binutils at sources dot redhat dot com
- Date: 30 Dec 2002 12:06:31 -0200
- Subject: Re: subdir/toplevel dependence (was Re: (toplevel)...)
- Organization: GCC Team, Red Hat
- References: <20021230103438.GA371@doctormoo>
On Dec 30, 2002, Nathanael Nerode <neroden@twcny.rr.com> wrote:
> I put this in because there's a real dependence here. :-(
Thanks, I see it now. It just happened to trigger other unwanted
dependencies, that I really disliked. Well, guess we'll have to put
them back in, but perhaps we can be more clever.
The idea is to force sub-configures to run whenever we run the
top-level configure, but if it's rerun just because the top-level
configure was updated, we don't have to rerun sub-configures, right?
That's the way it used to be.
The solution I see is to arrange for configure to remove sub-Makefiles
if it is run without --no-recursion (i.e., no_recursion != yes).
Then, the check for sub-Makefile in the configure-* targets will take
care of reconfiguring. How does this sound?
--
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