Michel wrote:
Hmm. Basically, whatever libGL's soname actually is, libGL itself (and
by extension this code) should know and thus be able to dlopen the
correct soname. I don't really like the idea of dlopening libGL.so
because it may pick up the wrong one with libGL.so.1 vs.
libGL.so.2,
On Tue, 2006-07-25 at 10:21 +0200, Michel Dänzer wrote:
On Sun, 2006-07-23 at 19:26 +0100, Alan Hourihane wrote:
On Sun, 2006-07-23 at 13:31 +0200, Michel Dänzer wrote:
On Sat, 2006-07-22 at 18:52 +0100, Alan Hourihane wrote:
Although should we try and open libGL.so first, and then
On Mon, 2006-07-24 at 07:21 -0700, Ian Romanick wrote:
The attached patch attempts to fix this in libGL by always dlopening
libGL itself with RTLD_GLOBAL before trying to dlopen the driver, and
dlclosing the handle obtained from dlopening libGL again before
returning. It works here,
On Sun, 2006-07-23 at 19:26 +0100, Alan Hourihane wrote:
On Sun, 2006-07-23 at 13:31 +0200, Michel Dänzer wrote:
On Sat, 2006-07-22 at 18:52 +0100, Alan Hourihane wrote:
Although should we try and open libGL.so first, and then
libGL.so.1 ??
Can you elaborate on what kind of
On Sat, 2006-07-22 at 18:52 +0100, Alan Hourihane wrote:
Seems like a good solution to me.
Thanks.
Although should we try and open libGL.so first, and then
libGL.so.1 ??
Can you elaborate on what kind of scenario you think that would be
necessary in?
--
Earthling Michel Dänzer
On Sun, 2006-07-23 at 13:31 +0200, Michel Dänzer wrote:
On Sat, 2006-07-22 at 18:52 +0100, Alan Hourihane wrote:
Seems like a good solution to me.
Thanks.
Although should we try and open libGL.so first, and then
libGL.so.1 ??
Can you elaborate on what kind of scenario you think
On Sat, 2006-07-22 at 18:11 +0200, Michel Dänzer wrote:
I think we need to get to the bottom of this problem, as it keeps
getting more annoying, e.g. now with AIGLX it's not always easy to tell
whether direct rendering is being used, and when it's not, bugs may take
down the server instead of
