Hi, > Again, it seems libGL loads that, not LO. LO just uses GLEW (and via > that libGL(U)) and those symbols are fullfilled. LO does not use > __driDriverGetExtensions_swrast itself, that is a mesa-internal.
yeah, you are right. This also explains the other bug where a totally different application was crashing the identical way. LOs only fault is (indirectly) using libGL. One can only wonder that there are not plenty more of problems and application crashes caused by simply linking/using libGL. Sorry for the noise then. In regards to the symbol consistency checks as required by the Debian policy it seems the mesa package does not quite conform to that then. Regards, Leon
