From owner-freebsd-current@FreeBSD.ORG Sat Nov 11 19:29:27 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CF9316A494; Sat, 11 Nov 2006 19:29:27 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FDD243EEF; Sat, 11 Nov 2006 19:28:19 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id kABJRwWH000566; Sat, 11 Nov 2006 14:27:58 -0500 (EST) Date: Sat, 11 Nov 2006 14:27:58 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Norikatsu Shigemura In-Reply-To: <20061112032442.04c4d246.nork@FreeBSD.org> Message-ID: References: <20061110151247.GA64530@zone3000.net> <20061111022044.8191e1c8.nork@FreeBSD.org> <20061111065629.GA82094@xor.obsecurity.org> <20061111235332.89f24170.nork@FreeBSD.org> <86lkmivws6.fsf@dwp.des.no> <20061112032442.04c4d246.nork@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-2.0.2 (mail.ntplx.net [204.213.176.10]); Sat, 11 Nov 2006 14:27:58 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: Dag-Erling =?ISO-2022-JP?B?U21fX3JncmF2?= , freebsd-current@freebsd.org, Kris Kennaway Subject: Re: libpthread vs libthr. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2006 19:29:27 -0000 On Sun, 12 Nov 2006, Norikatsu Shigemura wrote: > On Sat, 11 Nov 2006 12:33:37 -0500 (EST) > Daniel Eischen wrote: >> world. Then rebuild your ports. After that, all your ports will >> reference symbols in FBSD_1_0, and if libthr doesn't provide >> sched_yield@FBSD_1_0, it'll find it in libc. > > By the way, can gdm resolve sched_yield@FBSD_1_0 instead of > sched_yield@LIBTHREAD_1.0? I don't think so. Is there a > symbol resolving fallback mechanism which I don't know? See previous email. You have to rebuild all your ports. -- DE