<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [gl, glesv2] Cannot build with --gl and --glesv2" href="https://bugs.freedesktop.org/show_bug.cgi?id=57379#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [gl, glesv2] Cannot build with --gl and --glesv2" href="https://bugs.freedesktop.org/show_bug.cgi?id=57379">bug 57379</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>Btw. have you noticed that both openGL and GLESv2 libraries may provide some of the same named symbols? This might not be a problem with unified implementations like Mesa, but proprietary driver stacks might crash if you call a function from the wrong library. I don't really know, but I would be very very careful to not mix them. My point is, make absolutely sure by whatever means necessary, that a process does *not* link to both libGL.so and libGLESv2.so at the same time. I've had my share of problems with that, might have even been with Mesa. Note, if there is a problem, it will not explode at compile time. It might only explode when a call is made to the wrong library at runtime.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>