From owner-freebsd-sparc64@FreeBSD.ORG Fri Nov 2 13:34:26 2007 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 186C316A417 for ; Fri, 2 Nov 2007 13:34:26 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id EF32813C4C1 for ; Fri, 2 Nov 2007 13:34:25 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from bighuge.lonesome.com (cpe-66-68-146-180.austin.res.rr.com [66.68.146.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.soaustin.net (Postfix) with ESMTP id EA37D8C0F7; Thu, 1 Nov 2007 23:25:24 -0500 (CDT) From: Mark Linimon Organization: Lonesome Dove Computing Services To: freebsd-sparc64@freebsd.org Date: Thu, 1 Nov 2007 18:22:25 -0500 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200711011822.25884.linimon@lonesome.com> Cc: Christian Baer Subject: Re: Doesn't anything work around here? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 13:34:26 -0000 > What *really* annoys me about this is that noone has bothered to mark > the ports as "not working (yet)". I can remember that a fair while > back there was also still a setiathome port in the tree. If you tried > anything with that on sparc64 you got a message that it only worked > with i386. Sorry to come in on this discussion late. I am behind on email. I'm one of the people who goes through the ports and marks them broken -- at least on the basis of the build cluster runs. As of the last complete run on sparc64-6, I think I did indeed mark those. The latest sparc64-7 run is continuing. With the limited number of sparc64 machines we have, the elapsed time for even _incremental_ builds is on the order of 3-5 weeks, depending on what's changed in the meantime. Once that gets done, I'll probably do another pass. As for ports that compile and install correctly, but just don't work, we rely on our user base to file PRs. But there is a bit of chicken- and-egg problem: not many maintainers have access to these machines. Much more so than on i386, we are reliant on user fixes. I personally think it's still worth putting work into sparc ports, if for nothing else the potential for a solid, working, FreeBSD/sun4v down the road. But with the resources we have right now, the priorities are: i386, amd64, then sparc64. =46rom my intuition from the ports PR statistics, our user base ratio is about 25:10:1 for those three. (Best guess based on the numbers from ~6 months ago). mcl