Date: Mon, 5 Jun 2006 20:04:45 +0200 From: John Hay <jhay@meraka.org.za> To: Daniel Eischen <deischen@freebsd.org> Cc: current@freebsd.org Subject: Re: libpthread.so.2 compatibility Message-ID: <20060605180445.GA10089@zibbi.meraka.csir.co.za> In-Reply-To: <Pine.GSO.4.64.0606051322190.14745@sea.ntplx.net> References: <Pine.GSO.4.64.0606041156020.8602@sea.ntplx.net> <20060604174315.GA64158@zibbi.meraka.csir.co.za> <Pine.GSO.4.64.0606041423260.9199@sea.ntplx.net> <20060604191000.GA67836@zibbi.meraka.csir.co.za> <Pine.GSO.4.64.0606041902230.10482@sea.ntplx.net> <Pine.GSO.4.64.0606041914530.10482@sea.ntplx.net> <20060605164711.GA8065@zibbi.meraka.csir.co.za> <Pine.GSO.4.64.0606051253280.14745@sea.ntplx.net> <20060605171414.GA9032@zibbi.meraka.csir.co.za> <Pine.GSO.4.64.0606051322190.14745@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 05, 2006 at 01:33:13PM -0400, Daniel Eischen wrote: > > No, you can't use that app unless you somehow build it so that > it doesn't use libc. The problem is that you don't have a > libc.so.6 that matches libpthread.so.2. You -stable app depends > on libc.so.6, not libc.so.7. When you upgrade from -stable > to -current, you bypass the changes that went into libc.so.6 > before it became libc.so.7. The -current libpthread.so.2 > changed to stay in sync with those changes. > > Bottom line: -stable libc.so.6 != -current libc.so.6 > -stable libpthread.so.2 != -current libpthread.so.2 > > Both libpthread.so.2 and libc.so.6 (and .so.7) have to be > in sync (built from same-dated sources). Ok, hopefully this is just a temporary thing until somebody can work up the courage to bump libpthread.so.2. It is pretty silly to have two files with the same name but different contents. Even the compat libs cannot help with that. John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060605180445.GA10089>