On Thursday 11 October 2007 03:39:14 pm David O'Brien wrote: > On Thu, Oct 11, 2007 at 02:22:43PM -0400, John Baldwin wrote: > > On Thursday 11 October 2007 01:28:23 pm David O'Brien wrote: > > > On Thu, Oct 11, 2007 at 12:58:36PM +0400, Ruslan Ermilov wrote: > > > > On Wed, Oct 10, 2007 at 09:29:57AM -0700, David O'Brien wrote: > > > > > Shipping a libkse.so.3 in 7.0, would be yet another FreeBSD weirdism as > > > > > folks may wonder where .1 & 2 are. > > > > > > > > They are right here: > > > > > > > > /usr/ports/misc/compat5x/pkg-plist:%%SPARC64%%lib/compat/libkse.so.1 > > > > /usr/ports/misc/compat6x/pkg-plist.sparc64:lib/compat/libkse.so.2 > > > > > > Where did those come from? That is another weirdism as they don't exist > > > on i386: > .. > > These archs use libthr for libpthread because of lacking full libkse > > support, and install libkse as libkse as a result. They are analogous > > to libpthread.so.[12] on i386. Basically, libpthread was renamed to > > libkse on some archs and libthr on others in 7.0, and libpthread is now > > always a symlink. Given that, I think libkse should be libkse.so.3 in > > 7. > > Sparc64 is the only arch where this applies... I wonder how many sparc64 > users we have with threaded applications built on pre-releng7 that will > want to run them without recompiling... I think I have more fingers and > toes..
What about making libthr.so be .0 then on sparc64? That's what you would have to do if you wanted to maintain symmetry (because sparc64 didn't have a libthr, just a libpthread and a libkse). Given all that, I actually find it far less confusing to call them libkse.so.3 and libthr.so.3 (or 2 or whatever) and just symlinking libpthread to the default one. If we eventually remove the non-default one then the default one can become libpthread.so.3 instead of being a symlink. -- John Baldwin _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
