From owner-freebsd-sparc Thu Jan 27 20: 5:39 2000 Delivered-To: freebsd-sparc@freebsd.org Received: from bsd4us.org (cn386092-a.newcas1.de.home.com [24.40.46.90]) by hub.freebsd.org (Postfix) with ESMTP id 546EE15951 for ; Thu, 27 Jan 2000 20:05:36 -0800 (PST) (envelope-from lgriffin@BSD4US.ORG) Received: from localhost (lgriffin@localhost) by bsd4us.org (8.9.3/8.9.3) with ESMTP id XAA22686; Thu, 27 Jan 2000 23:00:50 -0500 (EST) Date: Thu, 27 Jan 2000 23:00:49 -0500 (EST) From: Lyndon Griffin To: Wes Peters Cc: Mark Tempel , freebsd-sparc@freebsd.org Subject: Re: Timeline for development In-Reply-To: <38910B7D.8D9A5929@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-sparc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org <:) Lyndon Griffin http://www.bsd4us.org On Thu, 27 Jan 2000, Wes Peters wrote: > port ASAP. Having a CVS repo or something like that for them to drop > stuff in as it is complete, or at least complete enough, will allow them > to contribute almost immediately. I'm going to try to get a server up this weekend... I'm new to CVS, unfortunately, but I'm sure I can hack my way through it... > > Oh please, just go with sparc-sun-freebsd. ;^) > Why not sparc-sun-unknown-freebsd? It should make you both happy. > No, but I can tell you your best bet is to pick a home for the cross tools > and dump the entire set of FreeBSD include files in that home somewhere. > When we start getting down to it, we can create the sparc specific include > files, comparing the alpha and i386 ones as a starting point. It might be > a good idea to start thinking about sparc vs. sparc64 early on as well. The elusive clue! Could this be the info I need to get the cross-compiler built? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message