From: Tomas Szepe <szepe@pinerecords.com>
To: rddunlap@osdl.org
Cc: Keith Owens <kaos@ocs.com.au>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: kbuild 2.5 release 2.4
Date: Sat, 4 May 2002 18:29:02 +0200 [thread overview]
Message-ID: <20020504162902.GB21542@louise.pinerecords.com> (raw)
In-Reply-To: <20020504121529.GA20335@louise.pinerecords.com> <Pine.LNX.4.33.0205040918450.22716-100000@osdlab.pdx.osdl.net>
> | 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.
T.
next prev parent reply other threads:[~2002-05-04 16:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 14:19 Keith Owens
2002-05-03 14:37 ` your mail tomas szepe
2002-05-03 15:07 ` tomas szepe
2002-05-03 15:29 ` Keith Owens
2002-05-03 15:45 ` tomas szepe
2002-05-03 15:57 ` kbuild 2.5 release 2.4 Keith Owens
2002-05-03 16:41 ` tomas szepe
2002-05-04 10:58 ` tomas szepe
2002-05-04 11:24 ` Keith Owens
2002-05-04 11:26 ` Zwane Mwaikambo
2002-05-04 12:11 ` Keith Owens
2002-05-04 11:58 ` Zwane Mwaikambo
2002-05-04 16:21 ` rddunlap
2002-05-04 11:39 ` tomas szepe
2002-05-04 12:00 ` Keith Owens
2002-05-04 12:15 ` tomas szepe
2002-05-04 16:19 ` rddunlap
2002-05-04 16:29 ` Tomas Szepe [this message]
2002-05-04 16:30 ` rddunlap
2002-05-05 2:27 ` Keith Owens
2002-05-04 13:01 ` Announce: Kernel Build for 2.5, Release 2.4 is available Keith Owens
2002-05-06 6:27 ` Keith Owens
2002-05-07 17:47 ` [kbuild-devel] " Thomas Duffy
2002-05-09 11:45 ` Keith Owens
2002-05-10 1:46 ` [kbuild-devel] " Thomas Duffy
2002-05-10 3:21 ` Keith Owens
2002-05-11 9:32 ` Keith Owens
2002-05-14 0:12 ` [kbuild-devel] " Thomas Duffy
2002-05-14 2:44 ` Keith Owens
2002-05-14 5:44 ` Keith Owens
2002-05-15 3:46 ` [kbuild-devel] " Thomas Duffy
2002-05-15 13:20 ` Keith Owens
2002-05-17 4:07 ` Keith Owens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020504162902.GB21542@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).