Hello, as you might have seen I performed build-xorg improvements and it is now possible to build Xvnc via those scripts. In my opinion prebuilt Xvnc will be built with this script so it's good time to discuss remaining issues.
"Statically" linked Xvnc now contains references for following libraries: $ readelf -a ./Xvnc |grep NEEDE 0x0000000000000001 (NEEDED) Shared library: [libpam.so.0] 0x0000000000000001 (NEEDED) Shared library: [libgnutls.so.26] 0x0000000000000001 (NEEDED) Shared library: [libgcrypt.so.11] 0x0000000000000001 (NEEDED) Shared library: [libdl.so.2] 0x0000000000000001 (NEEDED) Shared library: [librt.so.1] 0x0000000000000001 (NEEDED) Shared library: [libm.so.6] 0x0000000000000001 (NEEDED) Shared library: [libc.so.6] 0x0000000000000001 (NEEDED) Shared library: [ld-linux-x86-64.so.2] 0x0000000000000001 (NEEDED) Shared library: [libpthread.so.0] Everything except libgnutls.so.26 is present on old systems (i.e. RHEL4 & friends) so we must decide what to do with libgnutls. Although I'm not friend of static linking it seems we have to link Xvnc statically against libgnutls to avoid compatibility issues. I also created two patches which add -dridir and -xkbcompdir parameters to Xvnc. Those parameters should be determined same way as -fp parameter in vncserver script and passed to Xvnc. After vncserver gets improved UNIX code is ready for the alpha release, in my opinion. Regards, Adam -- Adam Tkac, Red Hat, Inc. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
