From owner-freebsd-hackers  Sun May 16  1:37: 6 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109])
	by hub.freebsd.org (Postfix) with ESMTP id 6E2C015152
	for <hackers@FreeBSD.ORG>; Sun, 16 May 1999 01:37:00 -0700 (PDT)
	(envelope-from dawes@rf900.physics.usyd.edu.au)
Received: (from dawes@localhost)
	by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id SAA19362
	for hackers@FreeBSD.ORG; Sun, 16 May 1999 18:36:58 +1000 (EST)
Message-ID: <19990516183658.I9622@rf900.physics.usyd.edu.au>
Date: Sun, 16 May 1999 18:36:58 +1000
From: David Dawes <dawes@rf900.physics.usyd.edu.au>
To: hackers@FreeBSD.ORG
Subject: Re: threads and Xlibs?
References: <373E705D.E8026F48@excite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <373E705D.E8026F48@excite.com>; from Dean Lombardo on Sun, May 16, 1999 at 08:14:37AM +0100
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, May 16, 1999 at 08:14:37AM +0100, Dean Lombardo wrote:
>Why does X have multi-thread support disabled by default?
>
>Quite a few programs (e.g. freeamp) give nasty "Xlib: unexpected async
>reply" errors due to making X calls from more than one thread.
>
>Now that threads and libc_r are part of the system (and have been for a
>while), perhaps Xlibs should be built thread-safe?
>
>Has anyone trying compiling XFree86 with multi-thread support enabled?

If someone who knows enough about the issues would like to sort this out,
then we at XFree86 will make the necessary changes.

David


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message