I compiled mesa cvs according to the build guide and "installed" it by setting LIBGL_DRIVERS_PATH, and when running quake 3 or tremulous, both games segfault while loading, during the creation of the main window. glxgears works fine with this driver, and unsetting LIBGL_DRIVERS_PATH allows both games to work fine. Attached are backtraces for quake3, icculus.org quake3, and tremulous.
Created attachment 6718 [details] backtrace of crash while running ioquake3
Created attachment 6719 [details] backtrace of crash while running closed source quake3
Created attachment 6720 [details] backtrace of crash while running tremulous
Are you making sure they're picking up the new libGL as well?
(In reply to comment #4) > Are you making sure they're picking up the new libGL as well? like I said, unsetting the LIBGL_DRIVERS_PATH env variable causes the programs to work
There have recently been changes to the GL dispatch mechanism which require libGL to be updated as well if the drivers are updated. So, please make sure the apps are using the newly built libGL.so.1 as well.
(In reply to comment #6) > There have recently been changes to the GL dispatch mechanism which require > libGL to be updated as well if the drivers are updated. So, please make sure the > apps are using the newly built libGL.so.1 as well. is this as easy as setting another env var? how do I do this?
You can try setting LD_LIBRARY_PATH, but these games may require LD_PRELOAD=/path/to/Mesa/lib/libGL.so.1 (as well?).
Thanks, while you were replying, I tried running export LD_LIBRARY_PATH=/path/to/Mesa/lib, and it fixed it. Quick response time, I might add..
err.. maybe fixed was the wrong resolution, you can change it if it's a big deal though, I guess... also, http://dri.freedesktop.org/wiki/Building#head-2ed4b11a128d7d28159498e7df102f15967088fb should be changed to include this step, if you don't have any problems I can add that to the page.
Sure, go ahead, thanks.
Mass version move, cvs -> git
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.