Dean Lombardo scribbled this message on May 16: > 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?
yeh, I did that a few months ago using the Xlib direct from the X Consortium, and it's a PITA... I can try updating the port, but there are SOO many hacks to the build environment, that it would probably be better for someone who actually knows the Xlib build environment to go over my patches... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
