From owner-freebsd-current Sun Dec 13 18:47:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16043 for freebsd-current-outgoing; Sun, 13 Dec 1998 18:47:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16038 for ; Sun, 13 Dec 1998 18:46:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA18566; Sun, 13 Dec 1998 18:46:54 -0800 (PST) (envelope-from dillon) Date: Sun, 13 Dec 1998 18:46:54 -0800 (PST) From: Matthew Dillon Message-Id: <199812140246.SAA18566@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: 'make clean' in /usr/src does not cleanup .o's or shared libs ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to do a buildworld with /usr/src mounted read-only (via NFS). The buildworld has died several times trying to remove .o files, binaries, and libraries (*.so.*) from /usr/src that happened to be hanging around. Ok, I say... cd /usr/src on the physical machine and 'make clean'. Only problem is it doesn't work... it does not recursive through the entire source hierarchy. For example, make clean in /usr/src does not bother recursing through /usr/src/bin, /usr/src/sbin, /usr/src/gnu, etc... It is *very* annoying. Is there any particular reason why make clean in /usr/src does not clean the entire source hierarchy? Also, having to restart the buildworld from scratch every time it blows up and exits is also quite annoying. It would be nice to have a 'rebuildworld' target that uses dot files similar to the way bsd.port.mk uses them to pick up where it left off. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message