From owner-freebsd-arch Tue Dec 5 19:20:15 2000 From owner-freebsd-arch@FreeBSD.ORG Tue Dec 5 19:20:14 2000 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id AC0D837B401; Tue, 5 Dec 2000 19:20:13 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id WAA00210; Tue, 5 Dec 2000 22:19:52 -0500 (EST) Date: Tue, 5 Dec 2000 22:19:52 -0500 (EST) From: Daniel Eischen To: Robert Watson Cc: freebsd-arch@FreeBSD.ORG Subject: Re: Threads in the base system In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Dec 2000, Robert Watson wrote: > Recently, pppctl was made thread-enabled, meaning that it relies on > libc_r. This makes the NOLIBC_R cannot be used with buildworld anymore. > Given that making pppctl depend on !NOLIBC_R may not be all that helpful, > it looks like we may need to lose NOLIBC_R. Presumably over time, threads > in default system applications will only become more popular. Any > thoughts (especially in light of upcoming KSE changes, which will make > threading integral to the system architecture)? OK, lose NOLIBC_R -- not that I'm biased or anything ;-) -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message