[Mesa3d-dev] glX TLS disabled by default?

[Adam Jackson]

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?  Most systems
> > support TLS these days, do they not?  Further, I'm not sure if this is
> > shared but my opinion is that the default configurations should cater
> > to the common case.
> 
> 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.  If
> a non-TLS X server loads a TLS Mesa driver, it will fail with unresolved
> symbols.

There's no intrinsic reason that the GLX loader couldn't support both, I
suppose, but it would be kind of lame.  There's still an interaction
between TLS and selinux that prevents me from shipping it, but I'm sure
that's fixable.

Mesa does attempt to be buildable for more systems than the X server
though.  I don't know if (for example) OpenVMS has sensible TLS support.

- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.x.org/archives/xorg-devel/attachments/20091109/74cd5a6c/attachment.pgp