Date: Thu, 2 Nov 2000 21:36:57 -0800 (PST) From: John Polstra <jdp@polstra.com> To: current@freebsd.org Cc: sobomax@freebsd.org Subject: Re: ABI is broken?? Message-ID: <200011030536.eA35avL10562@vashon.polstra.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011030536.eA35avL10562>