Note that "XTHREADS" does not mean Xlib will suddenly use threads, it really means
"make Xlib thread safe, by making LockDisplay() etal into real lock calls instead
of no-ops."
If Xlib isn't built with XTHREADS defined, it's not thread safe, so would be
unsafe to use in the highly threaded Java at all, wouldn't it?
Note that "XTHREADS" does not mean Xlib will suddenly use threads, it really means
"make Xlib thread safe, by making LockDisplay() etal into real lock calls instead
of no-ops."
If Xlib isn't built with XTHREADS defined, it's not thread safe, so would be
unsafe to use in the highly threaded Java at all, wouldn't it?