In article <[EMAIL PROTECTED]>, Maxim Sobolev
> 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.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to