From owner-freebsd-current Sat Nov 14 17:18:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06107 for freebsd-current-outgoing; Sat, 14 Nov 1998 17:18:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06101 for ; Sat, 14 Nov 1998 17:18:05 -0800 (PST) (envelope-from ggm@azure.dstc.edu.au) Received: from azure.dstc.edu.au (azure.dstc.edu.au [130.102.176.27]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id LAA25223 for ; Sun, 15 Nov 1998 11:17:42 +1000 (EST) Received: (from ggm@localhost) by azure.dstc.edu.au (8.8.5/8.8.4) id LAA01412 for current@freebsd.org; Sun, 15 Nov 1998 11:17:40 +1000 (EST) Date: Sun, 15 Nov 1998 11:17:40 +1000 (EST) From: George Michaelson Message-Id: <199811150117.LAA01412@azure.dstc.edu.au> To: current@FreeBSD.ORG Subject: once elf transited, does /usr/src/obj/{aout,elf} need to exist? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've completed the elf transition. If I blow away obj/{aout,elf,usr} will I get them back? I assume the aout build is a once-only, and there won't be a need to keep re-making the compat state? Hang on. if somebody tweaks something that requires a new libc in elfland to work, then non-upgraded aout binaries would need to see the change too wouldn't they? Bummer. that 150+mb isn't headroom after all... -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message