Top Level Autoconfiscation Status

Nathanael Nerode neroden@doctormoo.dyndns.org
Mon Jul 1 09:14:00 GMT 2002


On Mon, Jul 01, 2002 at 10:03:07AM -0600, Jeff Law wrote:
> In message <20020630221237.A2110@hollebeek.com>, Tim Hollebeek writes:
>  >> * To avoid a lot of subtle problems, configure uses absolute pathnames
>  >> for most directories which it puts into the Makefile.  This means you
>  >> can no longer 'configure', relocate srcdir or builddir, and then 'make'.
>  >> I doubt that this is important.
> I do this regularly -- especially on machines where configure is slow
> (hpux, aix, solaris).
I can figure out how to fix this. :-)  

>  >It could cause problems with mounted directories, which can have
>  >different names on different machines.  E.g. if I do a "make" in
>  >/usr/export/src/gcc and then try to do a "make install" in
>  >/net/src/gcc on a different machine.
> Also a real problem.

I can figure out how to fix this too.  The trick is doing it without
slowing 'make' down by approximately two orders of magnitude.  :-P

Looking at the issues I now have to resolve, I'm going to target the
actual inclusion of autoconfiscation into mainline for the beginning of
gcc 3.3 stage 1.  However, I'm going to try to push as many cleanups as
possible into CVS before that, since each thing I clean up beforehand
saves about 8 hours of testing of the final product. :-)

Speaking of which, could I please get review/approval for
http://gcc.gnu.org/ml/gcc-patches/2002-06/msg01910.html
http://gcc.gnu.org/ml/gcc-patches/2002-06/msg01738.html
http://gcc.gnu.org/ml/gcc-patches/2002-06/msg01970.html
sometime soon.

None of them change *any* behavior, and they make future work a *lot*
easier for me, but I'm a little uncomfortable committing them as
'obvious' because of their size.  (Plus which they have to get put into
src which I don't have write access to).

After that I'm thinking maybe I should just start a 'configury
cleanup branch'.  Until the reorg patches above, though, merging changes
from it will be a nightmare, so...

Thanks everyone for the feedback.  Very helpful.

--Nathanael



More information about the Gcc mailing list