Date: Tue, 4 Apr 2000 22:06:18 -0700 From: "David O'Brien" <obrien@freebsd.org> To: kdulzo@gerp.org Cc: freebsd-sparc@freebsd.org Subject: Re: Cross compilation problems Message-ID: <20000404220618.A5141@dragon.nuxi.com> In-Reply-To: <20000404233015.A26562@mobile.gerp.org>; from kdulzo@mobile.gerp.org on Tue, Apr 04, 2000 at 11:30:15PM -0500 References: <003301bf9ace$8325db60$49ec62d1@dirac> <20000331144005.577D437B7E8@hub.freebsd.org> <20000331173629.B50505@mobile.gerp.org> <20000404141505.B1423@dragon.nuxi.com> <20000404233015.A26562@mobile.gerp.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 04, 2000 at 11:30:15PM -0500, Kevin M. Dulzo wrote: > In any case, is the BSDi merger not lingering some unknown sparc kernel > bits to head our way? TBD. Things in the merging of the src are still being worked out. IMHO, we should proceed the way we would have before the merger. > And would we not be in good shape to hold off on possible redoubled > development efforts IMHO, no. FreeBSD/sparc must still feel and work like FreeBSD. It will take quite some time until FreeBSD/sparc is where FreeBSD/i386 is today. So having a crud somewhat working sparc port is still useful when the BSDI sparc bits become availble as the FreeBSD bits would probably provide the framework for the end product. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000404220618.A5141>