On Sun, Apr 6, 2014 at 10:11 AM, Michael DePaulo <mikedep...@gmail.com> wrote: > On Sun, Apr 6, 2014 at 8:58 AM, Michael DePaulo <mikedep...@gmail.com> wrote: > . >> However, after trying lots of things out, I managed to compile VcXsrv >> 1.14.3 (2013-09-20) with Windows XP support, and with the fixes for >> CVE-2013-4396 (2013-10-08) & CVE-2013-6462 (2014-01-07). >> >> I also determined that VcXsrv 1.14.3 already included the fixes for >> CVE-2013-1981..2005, CVE-2013-2062..2066 (2013-05-23). Therefore, my >> bulid contains 0 known vulnerabilities! >> >> I am calling my build 1.14.3.1. The build is here: >> http://code.x2go.org/releases/binary-win32/3rd-party/vcxsrv-modified-by-x2go-project/ >> >> And for now, the source code is here: >> https://sourceforge.net/u/mikedep333/vcxsrv/ci/xp-fixesonly/tree/ >> >> I updated X2Go-WinBuilder VM to use my 1.14.3.1 build. The X2Go Client >> nightly build with 1.14.3.1 is here: >> http://code.x2go.org/releases/binary-win32/x2goclient/heuler/mingw32-4.4/qt-4.8/x2goclient-4.0.2.0-2014.04.06-setup.exe >> >> >> Here's more information on my decision to create this VcXsrv build: >> 1. MSVC 2012 can produce XP compatible builds as long as you are using >> version "Update 1" or later, and you specify the v110_xp platform >> toolset. This is what I used for my 1.14.3.1 build. >> 2. VcXsrv 1.14.2.1 is the last version with XP support because it is >> the last version built with MSVC 2010. VcXsrv 1.14.3 was built with >> MSVC 2012 and VcXsrv 1.14.4 was built with MSVC 2013. The VcXsrv >> project's homepage still states that they are built with MSVC 2012, >> but the commit messages specify otherwise. >> 3. Although only the VcXsrv build system / makefiles were updated for >> MSVC 2013 with VcXsrv 1.14.4, the build system is very large. >> Therefore, I did not try to modify VcXsrv 1.14.4 for MSVC 2012 & >> v110_xp compatibility. >> 4. VcXsrv 1.15's source code is incompatible with MSVC 2012 because it >> contains certain C99 statements. >> 5. It looks like VcXsrv normally builds using cmd.exe, rather than >> cygwin's bash shell. VcXsrv includes cygwin bash shell scripts, but >> they are outdated. gawk had trouble with the .bat files used during >> the build of xkeyboard-config, so I switched to using cygwin's bash >> shell for the build and updated those scripts. Building using cygwin's >> bash shell was successful, it used .sh files instead for the build of >> xkeyboard-config. >> >> -Mike#2 > > Hmm, I thought I compiled VcXsrv 1.14.3.1 correctly with the v110_xp platform > toolset, but when I go to start it on my XP SP3 32-bit VM (instead of > on my Windows 8.1 64-bit machine), I get the error: > > C:\Program Files\x2goclient\VcXsrv\vcxsrv.exe is not a valid Win32 > application. > > Similarly, x2goclient.exe states: > > Can't start X server > Please check your installation > > I will investigate further. It is a 32-bit executable though. > > -Mike
I've fixed the build scripts and makefiles so that it is now compatible with XP. The 3 URLs I specified previously have been updated. The version # is the same, 1.14.3.1 . _______________________________________________ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev