Date: Fri, 22 Apr 2005 11:27:27 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Scott Long <scottl@samsco.org> Cc: freebsd-arch@freebsd.org Subject: Re: libpthread version bump Message-ID: <20050422182727.GA2753@troutmask.apl.washington.edu> In-Reply-To: <42693837.7090400@samsco.org> References: <20050422103141.F5855@carver.gumbysoft.com> <20050422174209.GA97721@troutmask.apl.washington.edu> <42693837.7090400@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 22, 2005 at 11:45:27AM -0600, Scott Long wrote:
> Steve Kargl wrote:
> >
> >A workaround may be the use of libmap.conf to map libc.so.5
> >to libc.so.6.
> >
>
> Well, we are talking about formally ensuring that 5.x compatibility
> works for 6.0 when it's released. Telling users to do a hack with
> libmap doesn't really match what we need.
>
Having lived through the std{io,err,out} libc snafu, the
libm.so.2 snafu, and now the libc.so.5/libpthread.so.1
problem, I will once again suggest that *ALL* library
version numbers should be bumped when a new branch is
created.
Yes, the above suggestion is a hack workaround, but I
know that it works for me with one commercial application
that I can't simply recompile.
--
Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050422182727.GA2753>