https://www.dragonflydigest.com/2005/01/22/xorg-681-strong/ A running description of activity related to DragonFly BSD. Sun, 23 Jan 2005 16:27:19 +0000 hourly 1 https://wordpress.org/?v=7.0 https://www.dragonflydigest.com/2005/01/22/xorg-681-strong/comment-page-1/#comment-425 Sun, 23 Jan 2005 16:27:19 +0000 http://www.shiningsilence.com/dbsdlog/?p=904#comment-425 FreeBSD 4 and DragonFly have two versions of the runtime library, libc and libc_r. The former is single threaded, the latter allows multiple pure userland threads.
Now consider a library like Qt or GTK which wants to support both single- and multi-threaded programs. For this, it has to contain locking instructions and therefore link against something providing this functions. In the Good Old Days, this was libXThrStub. This library was linking with each X11 program requiring such a multi-threaded library, which did not itself link against libc_r.
To avoid this hassle, the stubs has been moved into libc directly, meaning that you can link certain multi-threaded libraries and programs directly against libc, but the function always return a failure code.

]]> https://www.dragonflydigest.com/2005/01/22/xorg-681-strong/comment-page-1/#comment-424 Sat, 22 Jan 2005 22:27:20 +0000 http://www.shiningsilence.com/dbsdlog/?p=904#comment-424 I don’t quite understand enough about the threading system to understand what is going on here. I thought FreeBSD had threads. Is this not true, or is DFly different enough in implementation that we have to do something different?

]]>