[Mesa3d-dev] glX TLS disabled by default?
tfogal at alumni.unh.edu
Mon Nov 9 09:52:02 PST 2009
Mark Kettenis <mark.kettenis at xs4all.nl> writes:
> > From: Adam Jackson <ajax at nwnk.net>
> > Date: Mon, 09 Nov 2009 10:51:13 -0500
> > On Sat, 2009-11-07 at 16:29 -0800, Ian Romanick wrote:
> > > tom fogal wrote:
> > > > Is there any reason TLS for glX is disabled by default?
> > > I vaguely recall there being some interaction with the X server.
> > > If Mesa is built for TLS, then the X server must also be built
> > > for TLS. [. . .]
> > There's no intrinsic reason that the GLX loader couldn't support
> > both, I suppose, but it would be kind of lame. [plus selinux issue]
> Is the TLS you're talking about here an abreviation for Thread Local
> Storage? If so then even OpenBSD doesn't have (sensible) support for
Yes, it is.
In the case that we're building against an X server, is there perhaps
some kind of configure-time test we could do? Then the Mesa default
could be `autodetect' instead.
More information about the xorg-devel