Symbol SavageInitStreamsNew from module /usr/X11R6/lib/modules/drivers/savage_drv.o is unresolved!
Symbol SavageInitStreams2000 from module /usr/X11R6/lib/modules/drivers/savage_drv.o is unresolved!
Symbol SavageInitStreamsOld from module /usr/X11R6/lib/modules/drivers/savage_drv.o is unresolved!
Should I submit a bug report?
Felix Kühling wrote:
Am Sa, den 30.10.2004 schrieb Daniel J. Michael um 0:51:
You are correct about the unresolved symbols, they seem to happen with the cvs code also (but I think they must be new in the last couple of weeks sometime). Here is the output of my LIBGL_DEBUG=verbose glxinfo:
[EMAIL PROTECTED] ~ $ LIBGL_DEBUG=verbose glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 1.1.27 savage (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/savage_dri.so
libGL error: dlopen /usr/X11R6/lib/modules/dri/savage_dri.so failed (/usr/X11R6/lib/modules/dri/savage_dri.so: undefined symbol: _mesa_DeleteObjectARB)
libGL error: unable to find driver: savage_dri.so
This also looks like it's not my fault. There was some breakage in recent Mesa CVS. Either try the latest CVS or maybe a version from 1 or 2 weeks ago. I'm going to avoid updating my copy of Mesa from CVS until the dust has settled a little.
[snip]
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
