On Fri, Apr 15, 2016 at 12:18 PM, Chuck Atkins <chuck.atk...@kitware.com> wrote: > The problem this is trying to solve is that they both get installed and > create an ambiguous situation for which one get's used: > > libGL.so -> libGL.so.1.5.0 > libGL.so.1 -> libGL.so.1.6.0 > libGL.so.1.5.0 > libGL.so.1.6.0
FWIW this very issue has caused me to be stumped for at least a few hours. Resolving it *somehow* would be fantastic. Note that only letting one build at a time doesn't fully resolve the issue - some clever enterprising individual will build it one way, install, then build the other way, install. (Or forgetful individual...) And end up with the same problem. Of course it'd be *most* ideal if we could just have a single libGL which did whatever we wanted it to when we wanted. But I'm guessing there's a reason it was done this way. -ilia _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
