https://bugs.freedesktop.org/show_bug.cgi?id=95266
--- Comment #12 from David Lonie <david.lo...@kitware.com> ---
(In reply to Jose Fonseca from comment #10)
> The proper way of using a custom libGL.so is to simply set LD_LIBRARY_PATH
> to the directory that has it:
>
> ln -sf libGL.so libGL.so,1
> LD_LIBRARY_PATH=$PWD ./vtkRenderingCoreCxxTests
> "TestTranslucentLUTDepthPeeling" -I
Just tried that here, no such luck:
$ ln -s libGL.so libGL.so.1
$ LD_LIBRARY_PATH=$PWD:$LD_LIBRARY_PATH apitrace trace --api gl
./vtkRenderingCoreCxxTests "TestTranslucentLUTDepthPeeling"
apitrace: loaded into /usr/bin/apitrace
apitrace: unloaded from /usr/bin/apitrace
apitrace: loaded into /ssd/src/VTK/build-tmp/mesa_bug/vtkRenderingCoreCxxTests
apitrace: tracing to
/ssd/src/VTK/build-tmp/mesa_bug/vtkRenderingCoreCxxTests.18.trace
vtkRenderingCoreCxxTests:
/build/apitrace/src/apitrace-7.1/build/wrappers/glxtrace.cpp:97195: void (*
_wrapProcAddress(const GLubyte*, __GLXextFuncPtr))(): Assertion `procPtr !=
(__GLXextFuncPtr)&glXCreateContextAttribsARB' failed.
Looks like you did get a trace from it, though, so I wonder what's different.
Thanks for uploading that, hopefully that will make it easier to track down!
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
