This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Do not stage the final build results
- From: Daniel Jacobowitz <drow at false dot org>
- To: Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>
- Cc: Ranjit Mathew <rmathew at gmail dot com>, GCC Development <gcc at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 15 Dec 2005 08:49:04 -0500
- Subject: Re: [PATCH] Do not stage the final build results
- References: <43A05EB6.6030903@lu.unisi.ch> <43A12EED.5090600@gmail.com> <43A13120.7030901@lu.unisi.ch>
On Thu, Dec 15, 2005 at 10:02:24AM +0100, Paolo Bonzini wrote:
>
> >I used to be able to do:
> >
> > cd $BUILD_DIR/$TARGET/libjava/testsuite
> > make -k check
> >
> >to run only the libjava testsuite.
> >
> >When I try the same under "stage3-$TARGET/libjava/testsuite"
> >now, it fails to find the appropriate "gcj". The full error
> >log is appended at the end of this message.
> >
> >
> This is a use case that I usually don't do. And Dan as well apparently.
>
> Putting the final build results into a stage directory is useless, we'll
> do it if the bootstrap is restarted, but if not we can leave the user
> with the same directory layout as in the old scheme (or as if you're not
> bootstrapping).
Just to be clear: the other thing you can do here is "make unstage".
stage/unstage should be harmless between builds and a new invocation of
make should generally force the correct state, so it's safe to adjust
them as necessary.
> 2005-12-15 Paolo Bonzini <bonzini@gnu.org>
>
> * Makefile.tpl (all, do-[+make_target+], do-check, install,
> install-host-nogcc): Don't invoke $(stage) at the end.
> * Makefile.in: Regenerate.
Looks good to me.
--
Daniel Jacobowitz
CodeSourcery, LLC