Building on Win 2008

[Kelly O'Hair]

I see no reason to build on Win 2008. Yes, someday it should work, but
anything you build is suspect because the official JDK7 builds will
eventually be done on Windows XP.
You could end up tracking down problems that are unique to building on
Win 2008 and have no value to the official JDK7 release.

Of course finding these problems now certainly has some value, and if all
you have is Win 2008, or we need to support building on Win 2008, then
this isn't a waste of time, just not immediately valuable to me at least. ;^)

We have been having some problems with the Windows updates lately too.
I tend to not let these updates install automatically on any machine I
do builds on, I let them get downloaded automatically, but not installed
automatically.
When I want the machine updated, I ask for it to happen.

I hadn't heard about this Terminal Services and cygwin problem
but I did hear about a problem with some SQL Update problem on XP.

-kto


Max (Weijun) Wang wrote:
> Hi All
> 
> Just install Win 2008 and VS.NET 2008 this afternoon and try to build 
> JDK. There're 2 tiny issues:
> 
> 1. cl.exe's version is 15.XXXX, not recognized by Compiler-msvc.gmk. 
> Duplicate the MS.NET 2003 lines in the file to accept 15.
> 
> 2. MSVCDIR is not defined in VS.NET 2008's vcvars.bat. Instead there's a 
> VCINSTALLDIR. ifndef MSVCDIR and ifdef VCINSTALLDIR, then set MSVCDIR := 
> $(VCINSTALLDIR).
> 
> and the build seems to go on happily.
> 
> Then I decide to install Terminal Services so that I can control the 
> machine from somewhere else. A restart is needed so I kill the build 
> process and restart the machine.
> 
> Unfortunately, cygwin cannot start anymore, google knows this but no 
> solution:
> 
> http://www.nabble.com/Bash-startup-problems-on-Windows-2008-server-td18110908.html 
> 
> 
> I'll try install MKS.
> 
> Thanks
> Max
>