Date: Fri, 15 May 2009 10:42:42 +0100 From: Craig Butler <craig001@lerwick.hopto.org> To: Mark Linimon <linimon@lonesome.com> Cc: "Adam K." <akranzel@gmail.com>, freebsd-sparc64@freebsd.org Subject: Re: Sun Fire 280R questions. Message-ID: <1242380562.40393.18.camel@main.lerwick.hopto.org> In-Reply-To: <20090512215255.GA31766@lonesome.com> References: <fbe499bd0905121206w4a6f0ffcwb22c261c6b816203@mail.gmail.com> <20090512215255.GA31766@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Mark Is there anyway we can link in with Fenners work to list the broken ports ? How are we looking build cluster wise, are we able to do complete port tree builds ? In previous emails its been said that port developers don't have access to sparc64 kit, I may be able to help out by providing a jailed environment hanging off the end of an adsl line... do you think that would be any use ? Kind Regards Craig B On Tue, 2009-05-12 at 16:52 -0500, Mark Linimon wrote: > On Tue, May 12, 2009 at 12:06:07PM -0700, Adam K. wrote: > > Any known issues with the ports system on Sparc64? > > Yes, numerous ones :-) It doesn't see as much use as i386 or amd64 > (by a long shot), and numerous ports assume that they are running on > i386, both due to integer size and byte ordering. You'll want to look > at portsmon.freebsd.org and www.freshports.org for more information. > Right now there's no current "what ports don't build on sparc64" page; > I need to update it. > > mcl > _______________________________________________ > freebsd-sparc64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 > To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1242380562.40393.18.camel>