From owner-freebsd-current Tue Jun 25 21:36:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA04434 for current-outgoing; Tue, 25 Jun 1996 21:36:25 -0700 (PDT) Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA04429 for ; Tue, 25 Jun 1996 21:36:21 -0700 (PDT) Received: (from mark@localhost) by linus.demon.co.uk (8.7.5/8.7.3) id FAA10413; Wed, 26 Jun 1996 05:20:57 GMT Message-Id: <199606260520.FAA10413@linus.demon.co.uk> From: mark@linus.demon.co.uk (Mark Valentine) Date: Wed, 26 Jun 1996 05:20:57 +0000 In-Reply-To: "Jordan K. Hubbard"'s message of Jun 25, 8:26pm X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: "Jordan K. Hubbard" Subject: Re: Building inside of /usr/src? Cc: Bruce Evans , freebsd-current@freebsd.org, nate@sri.mt.net Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From: "Jordan K. Hubbard" > Date: Tue 25 Jun, 1996 > Subject: Re: Building inside of /usr/src? > > Have you tried it? :-) > > > > $ cd ~/tmp > > $ mkdir src i386 i386/obj > > Uh, that's supposed to work automatically though. You shouldn't need > to know your architecture. Sure, it'll *use* the symlink (and I do > know since I looked at the code that implements this! :-) but there > was no infrastructure for creating the architecture specific links and > if it's not done transparently then it's not much use (at least not > unless you *like* answering user questions :-). This is a rather confused response. Please think beyond /usr/src and /usr/share/mk; pmake is used for far more than that, and breaking it will break third party application build systems. Mark. -- Mark Valentine at Home