In article <mtuu1g6bcxu.fsf@contents-vnder-pressvre.mit.edu>,
	"Nathan J. Williams" <nathanw@wasabisystems.com> writes:
> first, I don't know what the benefit is. A little looking around in
> libX11 found display-locking code, but it's not clear to me when that
> would be useful... from a multithreaded program that makes X calls
> from multiple threads?

Exactly.

> Is there anything that is known to fail without this?

I've encoutered applications which wanted to that when pthread
support was enabled.

> second, this will pull libpthread into every X-using application,

Yes, it does.

> it will impose the libpthread stack-size limit on programs with no
> need for that limit,

This sounds more like a problem with "libpthread" than with the
above change. When will it be fixed?

> and it will interfere with programs that are linked against a
> different libpthread (pth, for example) for whatever reason.

Yes, that's a problem indeed.

> This may be a good reason to have libc export it's dummy pthread
> stubs, so that X11 can link against it and libpthread isn't actually
> pulled in unless a program is really threaded.

Please go ahead and make that change.

	Kind regards

-- 
Matthias Scheler                                  http://scheler.de/~matthias/