The DRI version has changed between 4.2.1 and 4.3. That's why you get the unresolved symbols. The real way to fix this would be to port the SiS DRI driver to the new version. I don't know how difficult will be, I'd expect that it is doable, just that nobody done so yet. If you would like to look into it I'd suggest you join the DRI project. Thomas has done a great job turning the SiS driver from a piece of junk to a really usable one. It should be pointed out that he is doing this solely on his spare time. Now it is on some other volunteer to take over the maintenance of the SiS DRI module. The workaround you are proposing may make DRI work, it is certainly not the solution. Open source has become popular because it allows each of us to implement the features and functionailites we would like to have. So why go with a workaround when youc can have the real thing (with just a little bit more effort)?
BTW: Thomas understood that! That's why we have a working SiS driver today! Egbert. Chris Roddy writes: > after building the recent snapshot, I noticed that the DRI module for > SiS 300 & friends has been disabled in xfree86.cf. (after un-commenting > it, I found out why - eep) > > Thomas Winischhofer's excellent SiS-on-Linux site provides binaries and > source for all of the drivers needed to use DRI with the SiS 300; > however, the binary sis_dri.so is useful only for XFree compiled with > gcc 2.95. > > I used gcc 3.2.2 under redhat 9 to compile a new 2.4.21 kernel with the > necessary framebuffer driver, patched the xfree 4.3.99 snapshot with Mr. > Winischhofer's X driver source, and then built the SiS DRI module from > an (unpatched) Xfree 4.2.1 source tree and copied the resulting > sis_dri.so to the DRI modules directory of the 4.3.99 installation. the > SiS DRI module from 4.2.1 works near-flawlessly under X built from the > most recent snapshot; I'm not even using a standard SiS 300 card, but > rather a 305. > > how much trouble would it be to port this up (even unmodified) from the > old source? I am not very familiar with autoconf/automake, but to me it > looks like the pile-o'-unresolved-symbols when building the module > shipped with the more recent source owes mostly to changes in the > xc/lib/ directory structure and header files. > > regardless, I would like to make the resulting sis_dri.so available > publicly, as folks whose Xfree was built with gcc 3.2 might find it > useful; can I assume this is permitted by the license? > > thanks > CR > > _______________________________________________ > Devel mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/devel _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
