From owner-freebsd-current Tue Jun 9 02:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03544 for freebsd-current-outgoing; Tue, 9 Jun 1998 02:26:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03517 for ; Tue, 9 Jun 1998 02:26:51 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id TAA10694; Tue, 9 Jun 1998 19:30:10 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199806090930.TAA10694@cimlogic.com.au> Subject: Re: More problems with Threads on -current. In-Reply-To: from Simon Coggins at "Jun 9, 98 07:22:07 pm" To: chaos@oz.org (Simon Coggins) Date: Tue, 9 Jun 1998 19:30:10 +1000 (EST) Cc: jb@cimlogic.com.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Simon Coggins wrote: > So I noticed when I checked out the source code. I've gotten past that (the > guys who do pike write a workaround for using F_SETFD). Next problem I'm having > is with _thread_sys_select() it doesn't seem to be waking up when an FD is > active. I'll try and write some code to display this and will get back to you. I started a set of commits to -current, but freefall won't let me in to complete it. So if it wakes up after I've gone to sleep, people can expect that libc_r won't build and probably libc too. I'll finish the job as soon as I can get in. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message