From: <bug...@an...> - 2006-11-04 17:43:08
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8250 ------- Additional Comments From ran...@ya... 2006-11-04 09:43 ------- (In reply to comment #16) > That's strange. Are you sure it really picked up the right libraries? For > testing, you could always just set LIBGL_DRIVERS_PATH to the path where the > *_dri.so driver is (this won't work for libgl though, you could try > LD_LIBRARY_PATH for that). I can't see any reason why it would make a > difference wrt resoluton selection or something similar. I know I was using the new r200_dri.so module because of the drmCloseOnce symbol issue. And I must have been using libdrm-2.2.0 because I created an RPM for it and upgraded from the existing libdrm-2.0.2 package. I suppose I could try uninstalling all my original Mesa RPMs before installing CVS over the top. Failing that, can you think of anything other than Mesa that links against libdrm? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |