On Wed, Feb 16, 2011 at 09:14:22PM -0600, DRC wrote: > On 2/16/11 10:03 AM, Adam Tkac wrote: > >> (1) When Xvnc is built with build-xorg, add > >> --with-dri-driver-path=../lib/dri to the Xorg configure options > > > > That makes sence but you need to use ../lib64/dri on 64bit Linux. > > > > Another solution, as I wrote on > > http://www.mail-archive.com/tigervnc-devel@lists.sourceforge.net/msg01083.html > > is to use -dridir parameter. > > > > Both solutions are fine from my point of view. > > I think -dridir is the better solution. It occurred to me that hard > coding a relative path into Xvnc is a bit of a security risk. I've > ported the Xorg 7.5 patches for -dridir and -xkbcompdir to Xorg 7.4 > (unfortunately, I am still unable to build Xorg 7.5 on RHEL 4 or 5. I > think it's an autotools incompatibility, but I haven't had a chance to > dig into it.)
Building X.Org 7.5 on older systems, like RHEL 4/5 will probably fail because upstream doesn't care about backward compatibility much. In my opinion we can build Xvnc only on fairly new systems, like RHEL-6 (not sure about RHEL-5). Resulting static Xvnc will run on both RHEL-5 and RHEL-4. Is it acceptable for you? Otherwise we need to dive into X.Org and all it's dependencies and restore backward compatibility, which might be non-trivial task. > What I did was build a new version of the binaries that hard codes the > DRI path as /opt/TigerVNC/lib/dri, then if a user chooses to install the > binary tarball into a directory other than /opt/TigerVNC, they can > override the DRI path at run time using the -dridir option when starting > vncserver (or simply modify vncserver to do that for them.) +1, sounds fine for me. I'm adding the "-dridir" documentation to my "Documentation TODO" list. When users want GLX capable Xvnc they need to pass the -dridir parameter. Regards, Adam -- Adam Tkac, Red Hat, Inc. ------------------------------------------------------------------------------ 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
