Re: kbuild 2.5 release 2.4
Tomas Szepe (email@example.com)
Sat, 4 May 2002 18:29:02 +0200
> | 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? :)
> Too much policy here?
> | Would it be complicated to only kill the files the build knows it had
> | created?
> That's what I would expect.
Word. The purpose of all the 'clean' targets in Makefiles (distclean,
mrproper, etc.) everywhere has always been to get rid of the object/
build files, and the object/build files only.
Don't get me wrong, Keith, I believe kbuild 2.5's a terrific piece of
code, I'm just discussing what I've found myself to be in trouble with.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/