Messages in this thread | | | Date | Sat, 4 May 2002 14:15:30 +0200 | From | tomas szepe <> | Subject | Re: kbuild 2.5 release 2.4 |
| |
> >Or even worse, suppose $KBUILD_OBJTREE gets reset to some weird > >value by accident and my whole home dir goes bye bye upon make > >mrproper? > <sarcasm> > Suppose cp gets aliased to rm -rf / by accident and my entire system > goes bye bye upon cp? > </sarcasm>
Hmm, I don't think this analogy will do -- working with aliases involving fileutils as root is a way straight to hell, and hardly anyone ever walks it. With kbuild-2.5, however, I have to set $KBUILD_OBJTREE every time I want to build a kernel with objects out of the source dir -- and hey, is there a single person on this list who's never made a typo on the command line?
I don't know how to properly emphasize that this *is* asking for problems, but still I'd be surprised if I were the only one scared by files not connected to the build getting erased on make mrproper. Hello, anyone? :)
Would it be complicated to only kill the files the build knows it had created?
-Tomas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |