From owner-freebsd-current Thu Nov 2 1:18:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 192CB37B479 for ; Thu, 2 Nov 2000 01:18:50 -0800 (PST) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.109]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id eA2AJlt20984; Thu, 2 Nov 2000 12:20:05 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.0/8.9.3) with ESMTP id eA29HcZ00803; Thu, 2 Nov 2000 11:17:38 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A013131.B8BD0BD7@FreeBSD.org> Date: Thu, 02 Nov 2000 11:17:37 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John Polstra Cc: current@FreeBSD.org Subject: Re: ABI is broken?? References: <3A005026.47B9978C@FreeBSD.org> <200011011835.eA1IZl207585@vashon.polstra.com> <3A006A58.E8315ABA@FreeBSD.org> <200011011914.eA1JE7c07768@vashon.polstra.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > In article <3A006A58.E8315ABA@FreeBSD.org>, > Maxim Sobolev wrote: > > John Polstra wrote: > > > Overall I would lean toward putting the hack into pthread_mutex_lock. > > > Comments? > > > > Huh, why we can't just bump libc_r version number and put older (buggy) version into > > lib/compat as usually? This would not require any ugly hacks at all. > > 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. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message