From 3b14ab0254a131e458c4f5ffdee931e868206424 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Wed, 11 Nov 2020 01:13:43 +0100 Subject: libthreads: Remove libthreads is most probably completely broken, and not the long-term road anyway. * config.make.in (VERSIONING): Remove. * configure.ac: Test for pfinet assembly compatibility instead of libthreads assembly compatibility. Do not set VERSIONING. * libthreads: Remove directory. * Makefile (lib-subdirs): Remove libthreads. * doc/hurd.texi (Threads Library): Rename references to libthreads into libpthread. * release/rfloppy.copy: Do not objcopy lib/libthreads.so. * release/tool-Makefile (rfloppy-solib): Remove libthreads. --- doc/hurd.texi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/hurd.texi b/doc/hurd.texi index c3442c8c..77d2357a 100644 --- a/doc/hurd.texi +++ b/doc/hurd.texi @@ -823,14 +823,14 @@ the rest of the Hurd relies upon them quite heavily. @node Threads Library @section Threads Library -@scindex libthreads +@scindex libpthread @scindex cthreads.h All Hurd servers and libraries are aggressively multithreaded in order to take full advantage of any multiprocessing capabilities provided by the microkernel and the underlying hardware. The Hurd threads library, -@code{libthreads}, contains the default Hurd thread implementation, which -is declared in @code{}. +@code{libpthread}, contains the default Hurd thread implementation, which +is declared in @code{}. The Hurd uses POSIX pthreads, which are documented in a lot of places. @c Thomas, 26-03-1998 @@ -1306,7 +1306,7 @@ The @code{} file declares several functions which are useful for low-level I/O implementations. Most Hurd servers do not call these functions directly, but they are used by several of the Hurd filesystem and networking helper libraries. @code{libiohelp} requires -@code{libthreads}. +@code{libpthread}. @menu * I/O Users:: User authentication management. -- cgit v1.2.3