On Thu, Sep 16, 2010 at 03:14:02AM -0500, DRC wrote: > Once I can successfully get a static build going on RHEL 4 (still having > problems with the lack of gnutls_transport_set_global_errno), I'll look > into these issues. libgcrypt and libgnutls are definitely not > cross-compatible, so the -static switch to build-xorg will probably have > to accommodate those libs as well as the others. > > I'm hoping that the new Xorg 7.5 patches you just checked in will > eliminate the build issue I had previously that was preventing me from > using Xorg 7.5. If so, I will generate a static Xvnc binary and look > into linking statically with gnutls. I then want to try out the > security features to make sure they behave like I expect, and I'll be > cool with releasing the alpha at that point. > > What is the situation with respect to doing Windows builds? I have > never successfully managed to build WinVNC. Did those patches ever make > it into a release of MinGW?
My MinGW patch isn't accepted, yet. And I'm not sure if it will be accepted: https://sourceforge.net/mailarchive/message.php?msg_name=AANLkTikg0hAGpArLTqFSWn6IdSI5aNOwJk-3ZDl4rqrq%40mail.gmail.com I'm going to merge my "vcstudio_buildsys" branch to trunk so it should be possible to build winvnc with both MSVC and MinGW. Regards, Adam > On 9/15/10 9:06 AM, Adam Tkac wrote: > > 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 > > > > ------------------------------------------------------------------------------ > 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 -- 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
