From owner-freebsd-sparc64@FreeBSD.ORG Sun Nov 4 12:54:07 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 215BF16A418 for ; Sun, 4 Nov 2007 12:54:07 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 4373D13C4B9; Sun, 4 Nov 2007 12:54:05 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <472DC0EC.3070904@FreeBSD.org> Date: Sun, 04 Nov 2007 13:54:04 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Christian Baer References: <200711011822.25884.linimon@lonesome.com> <472DACD7.6040501@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-sparc64@freebsd.org 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: Sun, 04 Nov 2007 12:54:07 -0000 Christian Baer wrote: > On Sun, 04 Nov 2007 12:28:23 +0100 Kris Kennaway wrote: > >> ^^^^^ >>> Someone is working on FreeBSD/sparc32? >> FreeBSD does not support 32-bit sparc and it is unlikely it ever will. > > That's why I was a little shocked about the Sun4v. Was that a typo? No, sun4v is the latest sparc architecture. It is very much 64 bit ;) >>> I'm just wondering how two really common apps that have been broken for >>> quite a while now could just slip through the grid. >> Few people use sparc64 on their desktop. That means that if you want to >> do that you are running without the benefit of a large testing >> community, and you will have to shoulder part of that burden yourself. > > That would be fine with me. So I wasn't complaining about the ports > themselves being broken or even that noone had noticed Keepassx being > broken (although that doesn't even build on my machine). > > When I couldn't get Firefox and Thunderbird to run I googled around a bit > to find a solution. All I found out was that the broken port was known for > more than a year now. It wasn't a problem that nobody actually fixed it (I > know the sparc64 community on FreeBSD is still quite small) but that > nobody had marked the ports as broken. My complaint was actually that just > about everybody had to find out by themselves that these ports are broken. > I was annoying enough for me with a U60 with 450MHz CPUs. I wonder how > long it would have taken someone with a much slower machine to "find out". It has been broken and fixed many times over history. That is what I meant by "fragile", i.e. when someone fixes it in one version, later versions tend to become broken again. Kris