On Fri, 2003-10-31 at 14:45, Felix Kühling wrote: > On Fri, 31 Oct 2003 09:47:36 -0800 > Ian Romanick <[EMAIL PROTECTED]> wrote: > > > Alan Hourihane wrote: > > > On Thu, Oct 30, 2003 at 05:07:33PM -0800, Ian Romanick wrote: > > >>manu wrote: > > >> > > >>>Responding to myself : sorry it seems that the problem is because the > > >>>r200_dri.so module is linked against libexpat.so.1 which is not on my > > >>>system. So I just made a link to the one I had and all is working great > > >>>now! > > >>>glxgears gives me ~1535 FPS. Is it OK? (Radeon 9200 with 64MB). > > >>>Thanks for the help, and sorry for eating the bandwidth ;-) > > >> > > >>Ah! Actually, thank you very much. :) The problem seems to be that > > >>with libexpat.so missing, there are unresolved symbols in r200_dri.so. > > >>The dlopen of r200_dri.so in OpenDriver (lib/GL/dri/dri_glx.c, line 184) > > >>fails. HOWEVER, it only logs a message if LIBGL_DEBUG is set. I > > >>removed libexpat from my system and was able to recreate the crash. > > >>With LIBGL_DEBUG set I get a nice message about not being able to open > > >>the driver. > > >> > > >>My person opinion is that the error messages in OpenDriver (but not the > > >>ones in GetDriverName) should be printed regardless of the setting of > > >>LIBGL_DEBUG. That would have helped find the source of this problem > > >>much sooner. We basically got lucky that Manu figured out that libexpat > > >>was missing for himself. :) > > > > > > We should probably link against the static version of libexpat.a to > > > avoid this trouble. > > > > I was pretty sure that the snapshots did staticly link with libexpat.a. > > I remember there being some discussion about this. Once XFree86 4.4.0 > > hits the streets this particular problem will be moot. AFAIK, XFree86 > > 4.4.0 will include libexpat. > > I don't think that would solve these problems. It's more complicated > than whether libexpat installed or not installed. The .so file has > different names on different distributions. And even if XFree86 comes > with libexpat that doesn't mean that distributors compile/link it with > XFree's libexpat. They may as well link it with their own one instead > with its own distro-specific so-name. The only real "solution" for the > snapshots is to link libexpat statically. I discussed that with José > before and suggested a way to get it linked statically. Either it's not > implemented yet or the problems were reported with not quite recent > snapshots, don't know. Also, José mentioned that he had trouble > uploading new snapshots recently due to problems with SourceForge shell > servers.
Should sourceforge's shell servers continue to be a problem, pdx.freedesktop.org has a lot of capacity (cpu, disk) if there was a desire to move snapshots there. -- Eric Anholt [EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
