From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 14 15:29:07 2003 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB52016A4CE for ; Sun, 14 Dec 2003 15:29:07 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15F7A43D35 for ; Sun, 14 Dec 2003 15:29:06 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from localhost by pandora.cs.kun.nl id hBENT31o015470 (8.12.10/3.58); Mon, 15 Dec 2003 00:29:03 +0100 (MET) From: Adriaan de Groot To: amd64 freebsd Date: Mon, 15 Dec 2003 00:29:00 +0100 User-Agent: KMail/1.5.94 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200312150029.00388.adridg@cs.kun.nl> Subject: End of pthread troubles in ogg123 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 23:29:07 -0000 With the most-recent -CURRENT (well, from yesterday or so), and without recompiling ogg123, the libmap.conf switch between libc_r and libkse works fine, so I'd say the threading issues have been thrashed out. Thanks Peter. Only recent panic was while unplugging a USB pendrive, and that's more likely just general USB stack suckage than amd64 specific. -- pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot If the door is ajar, can we fill it with door-jamb?