From owner-freebsd-current@FreeBSD.ORG  Sat Nov 11 18:17:22 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 5075516A40F;
	Sat, 11 Nov 2006 18:17:22 +0000 (UTC)
	(envelope-from nork@FreeBSD.org)
Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 31D3B43D6B;
	Sat, 11 Nov 2006 18:17:21 +0000 (GMT)
	(envelope-from nork@FreeBSD.org)
Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com
	[219.127.74.122]) by sakura.ninth-nine.com
	(8.13.8/8.13.8/NinthNine) with SMTP id kABIHHqw085869;
	Sun, 12 Nov 2006 03:17:17 +0900 (JST) (envelope-from nork@FreeBSD.org)
Date: Sun, 12 Nov 2006 03:17:17 +0900
From: Norikatsu Shigemura <nork@FreeBSD.org>
To: Daniel Eischen <deischen@FreeBSD.org>
Message-Id: <20061112031717.10f128fc.nork@FreeBSD.org>
In-Reply-To: <Pine.GSO.4.64.0611111224560.6747@sea.ntplx.net>
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>
	<Pine.GSO.4.64.0611111224560.6747@sea.ntplx.net>
X-Mailer: Sylpheed version 2.3.0beta4 (GTK+ 2.10.6; i386-portbld-freebsd6.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2
	(sakura.ninth-nine.com [219.127.74.121]);
	Sun, 12 Nov 2006 03:17:18 +0900 (JST)
Cc: Dag-Erling, Norikatsu Shigemura <nork@FreeBSD.org>,
	freebsd-current@FreeBSD.org, Kris Kennaway <kris@obsecurity.org>,
	=?ISO-2022-JP?B?U21fX3JncmF2?= <des@des.no>
Subject: Re: libpthread vs libthr.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Nov 2006 18:17:22 -0000

On Sat, 11 Nov 2006 12:33:37 -0500 (EST)
Daniel Eischen <deischen@freebsd.org> wrote:
> The way to fix this for the above problem is to enable symbol
> versioning (set SYMVER_ENABLED=yes in /etc/make.conf) and rebuild
> 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.

	I don't know that this issue will fix.  But I know many problems
	with SYMVER_ENABLED=yes.

	1. java_vm is too unstable.
	   I couldn't compile OOo (editors/openoffice.org-2.0) once.
	   However, in disabled SYMVER_ENABLED=yes environment,
	   I could compile OOo once.

	2. some gtk applications are too unstable.
	   scim (textproc/scim and japanese/scim-canna) would crash
	   unexpenctedly.

	3. firefox (www/firefox) cannot connect(2) to servers.
	   firefox issue connect(2) system call.  But it failed.

	4. synergys (sysutils/synergy) is locked.
	   synergyc connected to synergys, and synergys was locked.

	I already reported above issues:
	http://lists.freebsd.org/pipermail/freebsd-current/2006-July/064605.html

	These issues are available with SYMVER_ENABLE=yes.  So I disabled
	SYMVER_ENABLE=yes, and these issues are fixed.