John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Maxim Sobolev <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
