From owner-freebsd-current  Thu Nov  2 21:37: 3 2000
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id 573BC37B4D7; Thu,  2 Nov 2000 21:36:59 -0800 (PST)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id VAA13440;
	Thu, 2 Nov 2000 21:36:58 -0800 (PST)
	(envelope-from jdp@wall.polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.11.0/8.11.0) id eA35avL10562;
	Thu, 2 Nov 2000 21:36:57 -0800 (PST)
	(envelope-from jdp)
Date: Thu, 2 Nov 2000 21:36:57 -0800 (PST)
Message-Id: <200011030536.eA35avL10562@vashon.polstra.com>
To: current@freebsd.org
From: John Polstra <jdp@polstra.com>
Cc: sobomax@freebsd.org
Subject: Re: ABI is broken??
In-Reply-To: <3A013131.B8BD0BD7@FreeBSD.org>
References: <3A005026.47B9978C@FreeBSD.org> <3A006A58.E8315ABA@FreeBSD.org> <200011011914.eA1JE7c07768@vashon.polstra.com> <3A013131.B8BD0BD7@FreeBSD.org>
Organization: Polstra & Co., Seattle, WA
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <3A013131.B8BD0BD7@FreeBSD.org>, Maxim Sobolev
<sobomax@FreeBSD.ORG> wrote:
> John Polstra wrote:
>
> > The bug wasn't in libc_r -- it was in libgcc_r.  That's a
> > static library, so it doesn't have a version number.  And it is
> > statically linked into old executables.  Nothing we do to libgcc_r
> > will help old executables, because they won't even use the new
> > libgcc_r.
>
> Nope it should help, because the bug is triggered if someone tries
> to use old executables with new libc_r.

Yes, I think you're right after all.  But since I've already worked
around the problem in libc_r, there's no need to do anything else at
this point.

John


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message