From owner-freebsd-current Thu Dec 14 12:24:36 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 14 12:24:34 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1C98D37B400 for ; Thu, 14 Dec 2000 12:24:34 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA26597 for ; Thu, 14 Dec 2000 12:24:40 -0800 Date: Thu, 14 Dec 2000 12:24:33 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: Old Business: followup about dirty 'modules' directory In-Reply-To: <388F6AB0.8B806F3B@scc.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A month or so ago I queried/complained about src/sys/modules getting corrupted with architecture specific derived files such that I could no longer share between i386 && alpha. Part of this issue had to do with having some idiocy on my part, but part of it *seems* to have to do with if you change the default /usr/obj to somewhere else. The setup I have here for all of my varied test machines is: private/per-machine /usr/src (CVS to local cvsup'd copy, ergo, out of date) shared, NFS mounted sys, mounted as /tstsys, and thence a loopback mount to a local directory for /tstsys/compile, CVS to freefall (ergo, could be kept up to the minute for all platforms) What was happening is that just one machine seemed to be polluting /tstsys/modules with derived files (.ko's, .depends, etc.). Big PITA. I queried and everyone said, "huh?", so I shut up and simply loopback mounted /tstsys/modules to a local directory for that machine as well. I finally decided that this was stupid, and looked into it more. It appears that this was the only machine that had a MAKEOBJDIRPREFIX set. Somehow this seemed to interfere with the dance that goes on with building modules for each kernel. I haven't tracked it further than this, but thought I should mention it in case anyone else has stubber their toe on this one. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message