[Mesa-dev] [PATCH] dri-vmwgfx: add __driDriverGetExtensions_vmwgfx() function

[Eric Anholt]

Brian Paul <brianp at vmware.com> writes:

> On 01/20/2014 06:19 PM, Matt Turner wrote:
>> I can't see why this would be needed at all. The X.Org loader was
>> modified to look for the new symbol names (i.e., the one added in this
>> patch) but still looks for the regular ones too.
>>
>> And since Jordan's patch to megadrivers, the X.Org loader doesn't even
>> need to look for the new symbol names
>
> I first saw this problem back in November at one point and I created the 
> patch then.  At some pointer after, I forgot about the patch and I 
> wasn't see the issue anymore.  I figured something in the DRI 
> infrastructure changed, thus making the patch obsolete.
>
> But then, just a week or so ago, a coworker was setting up a new devel 
> environment when it resurfaced for her:
>
> $ ./glxgears
> libGL: OpenDriver: trying /usr/lib/dri/vmwgfx_dri.so
> libGL: driver does not expose __driDriverGetExtensions_vmwgfx(): 
> /usr/lib/dri/vmwgfx_dri.so: undefined symbol: 
> __driDriverGetExtensions_vmwgfx
>
> Honestly, I haven't had time to dig into this to know if there's a stale 
> component somewhere that's responsible.

That's just the loader not being careful about it error messages -- it
throws the message even in the success case if the symbol isn't
present.  We should fix that.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20140121/731c9d9a/attachment-0001.pgp>