Date: Fri, 30 May 2003 19:58:57 -0400 (EDT) From: Daniel Eischen <eischen@pcnet.com> To: ports@freebsd.org Cc: threads@freebsd.org Subject: Transition plans: libkse->libpthread Message-ID: <Pine.GSO.4.10.10305301945590.10348-100000@pcnet5.pcnet.com>
next in thread | raw e-mail | index | archive | help
Sometime shortly after 5.1 release, we'll (hopefully) be installing libpthread as "libpthread" instead of "libkse" by default. There are some things that need to be fixed (signal handling) before this can happen, but we're working on it now. Locally, I install the library as libpthread, but this breaks lots of ports that use autoconf and/or libtool. I still have PTHREAD_LIBS unchanged (set to libc_r), but that doesn't seem to matter. What happens is that some things end up getting linked to both libpthread and libc_r, and compiler wackiness ensues also. To see what happens, try: # cp /usr/lib/libkse.so.1 /usr/lib/libpthread.so.1 # ln -s /usr/lib/libpthread.so.1 /usr/lib/libpthread.so and then rebuilding XFree86-4 and kde3.1. I suspect that we want PTHREAD_LIBS to always be obeyed, so that one could link to libc_r, libthr, or libpthread. Sure, one could use libmap, but applications that are linked to different threading libraries should be able to coexist. Anyway, this is just to give you guys some advance notice of future breakage. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10305301945590.10348-100000>