[PATCH] Do not stage the final build results
Paolo Bonzini
paolo.bonzini@lu.unisi.ch
Thu Dec 15 10:53:00 GMT 2005
>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).
Try the attached patch.
Paolo
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dont-stage-too-much.patch
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20051215/fa1266db/attachment.ksh>
More information about the Gcc
mailing list