This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Top Level Autoconfiscation Status
- From: Jeff Law <law at porcupine dot slc dot redhat dot com>
- To: Nathanael Nerode <neroden at doctormoo dot dyndns dot org>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 01 Jul 2002 14:54:21 -0600
- Subject: Re: Top Level Autoconfiscation Status
- Reply-to: law at redhat dot com
In message <20020701161217.GA5117@doctormoo.dyndns.org>, Nathanael Nerode write
s:
>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. :-)
"this" meaning slow configure or make relocation of the buildir work?
Typically I tar up a build tree, then un-tar it somewhere else, make a
tweak or two and run some tests.
[ install on different machine with different paths to directories ]
>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
FWIW, this one is actually more important to the end users -- it's come
up several times with Red Hat's customers. ie, they have a centralized
build machine. Once the tools are built, they log into each developer
machine and run "make install". The paths to the sources & build
directories are (of course) different on the developer machines vs the
centralized build machine.
jeff