From owner-freebsd-arch@FreeBSD.ORG  Fri Apr 22 19:16:40 2005
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1500916A4CE; Fri, 22 Apr 2005 19:16:40 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A6D4B43D31; Fri, 22 Apr 2005 19:16:39 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1])
	by harmony.village.org (8.13.3/8.13.1) with ESMTP id j3MJE8am043347;
	Fri, 22 Apr 2005 13:14:08 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Fri, 22 Apr 2005 13:14:08 -0600 (MDT)
Message-Id: <20050422.131408.39194704.imp@bsdimp.com>
To: deischen@freebsd.org
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <Pine.GSO.4.43.0504221419510.24214-100000@sea.ntplx.net>
References: <20050422103141.F5855@carver.gumbysoft.com>
	<Pine.GSO.4.43.0504221419510.24214-100000@sea.ntplx.net>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-arch@freebsd.org
Subject: Re: libpthread version bump
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Apr 2005 19:16:40 -0000

> > The recent changes to implement the the %fs/%gs manipulation syscalls has
> > created a problem for 5.x compatibility.  While libc has been bumped for
> > 6.x already, libpthread hasn't, so running 5.x apps on -CURRENT ends up
> > with the app pulling in the old libc correctly, but it pulls in the
> > current libpthread which depends on the new libc and the linker errors out
> > on the missing symbols.
> >
> > I think we need to bump libpthread's version to allow for compatibility in
> > 6. Then we can ship the old libpthread along with the old libc and the
> > Right Thing happens.
> 
> I wish someone would work on getting symbol versioning working
> so we don't have to keep bumping library versions for things
> like this :-)

Symbol versioning wouldn't help this case...

Warner