>>>>> "Jake" == Jake Hamby <hamby_at_aris.jpl.nasa.gov> writes:
Jake> I recently upgraded from Solaris 2.4 to Solaris 2.5 and just
Jake> noticed the Direct X library in /opt/SUNWdxlib. Basically, if
Jake> you set /opt/SUNdxlib/lib/dxlib/SunOS5.x in your LD_LIBRARY_PATH
Jake> variable ahead of the others, then X programs will link with a
Jake> special version of Xlib that allows them to access the local
Jake> screen as much as 50-175% faster by using Sun's DGA extension.
Well that sounds pretty interesting.
Jake> Needless to say that sounded pretty interesting so I added the
Jake> appropriate line to my .xinitrc, and it turns out that FVWM does
Jake> not like these libraries! FVWM 1.24r crashed after just a few
Jake> seconds (and seemed to take much longer to start up), and FVWM
Jake> 2.0.39 seemed to work okay, then crashed when I selected Exit.
Jake> In both cases, the entire screen froze and I had to kill the X
Jake> server from a remote login...
Hm. Not good at all.
Jake> According to the Direct Xlib answerbook, normal X11 applications
Jake> should not have any problems with these libraries, unless they
Jake> reach below the X11 API or attempt to extend it. I doubt that
Jake> FVWM does either of these things. Has anyone tried anything
Jake> similar with FVWM (I know an older version of Direct Xlib was in
Jake> Solaris 2.4, and perhaps earlier)?
I don't compile under Solaris (normally), and don't have access to
version 2.5 regardless, and haven't seen anyone else mention this
before either, but you could try modifying the makefile and linking
against those libs directly and seeing how well it links and runs
then.
Theoretically it shouldn't make a difference, but I'd try it anyways.
Also, try another window manager (like twm, olwm, or mwm) and see how
it reacts.
Hope this helps,
Chuck
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Wed Dec 20 1995 - 08:42:21 GMT