From owner-freebsd-sparc64@FreeBSD.ORG  Mon Oct 22 19:27:41 2007
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
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 A56DD16A419
	for <freebsd-sparc64@freebsd.org>; Mon, 22 Oct 2007 19:27:41 +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 E307F13C4B5;
	Mon, 22 Oct 2007 19:27:40 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <471CF9AC.6090704@FreeBSD.org>
Date: Mon, 22 Oct 2007 21:27:40 +0200
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Miles Nordin <carton@Ivy.NET>
References: <ffg2gk$1n1r$1@nermal.rz1.convenimus.net>
	<oq7ilfsp72.fsf@castrovalva.Ivy.NET>
In-Reply-To: <oq7ilfsp72.fsf@castrovalva.Ivy.NET>
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 <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>, 
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2007 19:27:41 -0000

Miles Nordin wrote:
>>>>>> "cb" == Christian Baer <christian.baer@uni-dortmund.de> writes:
> 
>     cb> What *really* annoys me about this is that noone has bothered
>     cb> to mark the ports as "not working (yet)".
> 
>     cb> Why hasn't anyone done that with these (and possibly other)
>     cb> ports yet?  Thunderbird and Firefox have been broken for ages
> 
> sometimes there are reports of them working (a little).  but, yeah, it
> is reasonable to want to know, even before buying hardware much less
> compiling, whether this port has a working browser or not.
> 
> Isn't there some spot in the FreeBSD base system where you have to
> choose your thread library, and one works better on sparc64 than the
> other?  Is the thread library that works best on sparc64 set as the
> default right now?

There is only one choice on sparc64.  It is likely to be something 
within firefox (and related common code) since this is notoriously 
fragile on !x86.

Kris