[Mesa3d-dev] glX TLS disabled by default?

[Dan Nicholson]

On Mon, Nov 9, 2009 at 9:52 AM, tom fogal <tfogal at alumni.unh.edu> wrote:
> 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?
> [snip]
>> > > 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
>> it.
>
> 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.

Make it a variable in gl.pc and query it from the xserver configure.

gl.pc:
...
glx_tls = yes

xserver/configure:
if test "x$GLX_USE_TLS" = xauto; then
    GLX_USE_TLS=`$PKG_CONFIG --variable=glx_tls gl`
    test -z "$GLX_USE_TLS" && GLX_USE_TLS=no
fi

Or something like that.

--
Dan