Either that or apps can work around buggy libGLs by checking the client
extension string for GLX_ARB_get_proc_address. That extension is
client-side only, so that's good enough.
Well, this is the output of a glxinfo from an user with the bug :
name of display: :0.0
display: :0 screen: 0
Lionel Ulmer wrote:
Either that or apps can work around buggy libGLs by checking the client
extension string for GLX_ARB_get_proc_address. That extension is
client-side only, so that's good enough.
Well, this is the output of a glxinfo from an user with the bug :
[snip]
And you can see that
I'd point you to the patches if I could remember when this last came
up. If someone has time they might look through the dri-devel or
dri-users archives. Does anyone on dri-devel remember this issue and
what the fix was? glXGetProcAddressARB not being available.
Alex
--- Mike A. Harris [EMAIL
On Fri, Nov 14, 2003 at 01:11:24PM -0800, Alex Deucher wrote:
I'd point you to the patches if I could remember when this last came
up. If someone has time they might look through the dri-devel or
dri-users archives. Does anyone on dri-devel remember this issue and
what the fix was?
Lionel Ulmer wrote:
On Fri, Nov 14, 2003 at 01:11:24PM -0800, Alex Deucher wrote:
I'd point you to the patches if I could remember when this last came
up. If someone has time they might look through the dri-devel or
dri-users archives. Does anyone on dri-devel remember this issue and
what the
