IIRC, there is some way to override this path, either at build time or run time or both. I will look into it and see if I can build the DRI library into the distribution. I didn't really care about it because I always just use VirtualGL, but the software renderer really should work for the purposes of completeness.
On 2/14/11 3:51 PM, Robert Goley wrote: > This is an annoying problem I ran into when I was building and > distributing to a couple of machines. Using the build-xorg scripts, it > leaves the path hard set to the location of the xorg libraries/modules > instead of setting a path and installing them to it with the main > tigervnc program. Because these are runtime dynamic load libraries, you > do not see an error until you attempt to run the server with those > extensions enabled. A quick fix for your testing would be to get the > /tmp/tigerbuild.c27921/tigervnc-1.0.90/linux64/xorg.build directory from > DRC and extract it to the same path. I would like to find a more > permanent way to fix this problem but it should only be an issue on > distributions that have a version of xorg too old to build the Xvnc > program against it... ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
