On Thu, 15 Jul 1999, Jordan K. Hubbard wrote:
:->> Jordan should have to say something about this. AFAIR, bumps are
:->> allowed but only by one between releases. We will have to provide
:->> libc_r.so.3 in /usr/lib/compat/compat3x, though (we'll have to do this
:->> anyway by the time 4.x is rel
> Jordan should have to say something about this. AFAIR, bumps are
> allowed but only by one between releases. We will have to provide
> libc_r.so.3 in /usr/lib/compat/compat3x, though (we'll have to do this
> anyway by the time 4.x is released).
I'd prefer not to bump it... John Birrell and I
Thomas Gellekum <[EMAIL PROTECTED]> writes:
> libc_r.so.3 in /usr/lib/compat/compat3x, though (we'll have to do this
/usr/src/lib/compat/compat3x
Sorry.
tg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Daniel Eischen <[EMAIL PROTECTED]> writes:
> The libc_r version number was bumped in -current because of the
> addition of poll(). Is this allowed in -stable, or something
> that waits for a -RELEASE?
Jordan should have to say something about this. AFAIR, bumps are
allowed but only by one betwe
Thomas Gellekum <[EMAIL PROTECTED]> wrote:
> Daniel Eischen <[EMAIL PROTECTED]> writes:
>
> > There are some bugs in libc_r in stable that have been fixed in
> > -current. I think the one that you've hit is an uninitialized
> > TAILQ_HEAD in a statically declared mutex (in localtime). It's
> >
