[PATCH 3/3] glx: Initialize glx even if there are currently no screens attached

[Adam Jackson]

On Sun, 2016-10-09 at 12:51 -0700, Jeremy Huddleston Sequoia wrote:
> Failure to do so causes an overvlow in glxClientCallback

This patch makes no sense at all. glxClientCallback is only added to
the call chain _after_ we check for a GL-capable visual. If that check
is preventing GLX from initializing, then it also prevents
glxClientCallback being called.

More to the point, the check is still correct, Mesa still needs a TC/DC
visual to work. I suppose non-Mesa systems might not have that
property, but a) OSX doesn't support pseudocolor GL rendering I am like
99% sure and b) that just means the check belongs in screen init
instead of being deleted entirely.

What are you trying to do here?

- ajax