From owner-freebsd-hackers Fri Jun 22 12: 1:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C511337B403 for ; Fri, 22 Jun 2001 12:01:18 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5MJ1BI73828; Fri, 22 Jun 2001 12:01:11 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200106221842.f5MIgaV58508@harmony.village.org> Date: Fri, 22 Jun 2001 12:11:36 -0700 (PDT) From: John Baldwin To: Warner Losh Subject: Re: Two Junior Kernel Hacker tasks.. Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 22-Jun-01 Warner Losh wrote: > In message John Baldwin writes: >: 2) Build kernels in sys/compile/${MACHINE_ARCH}/FOO rather than >: sys/compile/FOO. > > Please use ${MACHINE}, not ${MACHINE_ARCH}. That way I can build > GENERIC for both i386 and pc98 at the same time without resorting to > the GENERIC98 hack I use now. Sure, sounds good. Actually, with mjacob's suggestion, I would go with sys/${MACHINE}/compile/FOO >: This is very helpful when you share the same sys/ tree across several >: machines with different architectures. For example, I share the same >: sys/ >: tree via NFS across almost all my testboxes including alpha and i386. >: Every >: time I want to compile GENERIC (I keep kernel.GENERIC up to date on my >: boxes) >: as part of an installworld I have to go manipulate symlinks (and/or >: shuffle >: directories around). Fixing this would make life for the non-x86 centric >: types a bit easier, although there'll probably be a big bikeshed over >: changing the build directory. *sigh* >: > > I'd be up for doing this, so long as I got to choose where to build > into :-) > > sys/arch/${MACHINE}/compile/FOO > > but that would start the arch bikeshed. I'd love to just do it. I would tackle the sys/arch bikeshed on its own merits for now. (BTW, I favor sys/arch FWIW). If we use the path I proposed above (sys/MACHINE/compile/FOO) then if we do a sys/MACHINE -> sys/arch/MACHINE move we get the compile directory move for free. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message