This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Changes introduced with b-i-b merge
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- To: gcc at gcc dot gnu dot org
- Date: Thu, 19 Dec 2002 18:56:45 -0600 (CST)
- Subject: Re: Changes introduced with b-i-b merge
- Reply-to: rittle at labs dot mot dot com
Hi DJ,
> If you still see reconfigures, we need to know which subdirs are
> being reconfigured (the first one reconfigured is probably the
> broken one).
OK, I see now that this is an FAQ issue being addressed (Thanks! ;-)
but since you asked. In order, seen after running top-level gmake:
top-level and gcc are not reconfigured.
libiberty is reconfigured, nothing else rebuilt due to this reconf.
libstdc++ is reconfigured, nothing else rebuilt due to this reconf.
libf2c is reconfigured, *everything* is rebuilt due to this reconf.
(everything being rebuilt after reconf is not new; reconf every gmake is.)
libffi is reconfigured, nothing else rebuilt due to this reconf.
boehm-gc is reconfigured, nothing else rebuilt due to this reconf.
zlib is reconfigured, nothing else rebuilt due to this reconf.
libjava is reconfigured, all C++ code rebuilt; Java code not rebuilt.
For the record, I don't mind waiting the few seconds for the extra
reconfigurations; it is the secondary effects that are quite painful
IMHO.
Regards,
Loren