From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 4 May 2002 07:40:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 4 May 2002 07:40:05 -0400 Received: from louise.pinerecords.com ([212.71.160.16]:15370 "EHLO louise.pinerecords.com") by vger.kernel.org with ESMTP id ; Sat, 4 May 2002 07:40:05 -0400 Date: Sat, 4 May 2002 13:39:54 +0200 From: tomas szepe To: Keith Owens Cc: lkml Subject: Re: kbuild 2.5 release 2.4 Message-ID: <20020504113954.GB20042@louise.pinerecords.com> In-Reply-To: <20020504105857.GC17252@louise.pinerecords.com> <23627.1020511496@ocs3.intra.ocs.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-OS: Linux/sparc 2.2.21-rc3-ext3-0.0.7a SMP (up 12 days, 5:52) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > >Duh... I failed to demonstrate the real problem: kbuild-2.5's mrproper > >also erases *non-zero-size* files in the object tree: > With a separate object tree, everything in the object directory is > generated by kbuild. make mrproper deletes everything. Suppose I have scripts to automate kernel building in that dir? 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? Suppose many other scenarios, this "feature" can't stand -- it's inconceivable that you'd just do "rm -rf $KBUILD_OBJTREE". And I can't see why you would even try, given you "know" the names of the files generated anyway. T.