URL:   http://hg.openjdk.java.net/jdk8/build/rev/bd32ef0789ca
User:  erikj
Date:  2012-12-05 17:25:02 +0000

                                     

URL:   http://hg.openjdk.java.net/jdk8/jdk8/rev/bd32ef0789ca
User:  katleman
Date:  2012-12-05 21:45:09 +0000

                                     

I'm assuming kernel32.lib is in several places and we most certainly don't want to pick it up from the 2003-dir. When reading the log you posted here, configure is trying to pick it up from C:\Program Files\Microsoft SDKs\Windows\v7.1\Lib, that is why I asked if it was there or not. If it's not there we need to figure out why so that we can improve the logic in configure that tries to figure out the correct environment.
                                     

Looking closer at the posted log, it seems configure is ignoring your presetup path and is instead finding windows sdk 7.1. From what I can see, the paths are correct provided sdk 7.1 is installed and functioning. Could you verify that kernel32.lib is actually in C:\Program Files\Microsoft SDKs\Windows\v7.1\Lib?
                                     

kernel32.lib is here,
./Program Files/Microsoft Visual Studio .NET 2003/Vc7/lib/kernel32.lib

BUT that is not the compiler we wish to use, that one is here:
% which cl
/cygdrive/c/Program Files/MSVS10/VC/BIN/cl
                                     

It looks like the environment for running cl isn't getting set up correctly by configure. Without access to the system, debugging this will be hard.
                                     

This system has both VS2003 and VS2010, it appears to me that configure has picked up
VS2003 and is trying to use VS2010, and it also appears that it has picked this up from
the Windows registry. Can I do something to workaround this ?
                                     

Made P2  until we have a root cause.

                                     

These lines don't look good:

LINK : fatal error LNK1104: cannot open file 'kernel32.lib'
...
OS_VERSION_MICRO='16(0'
...
configure:18804: error: C compiler cannot create executables


Not sure if this is related to the non-standard install location for VS2010, or something to do with 32bit vs. 64bit building.
Googling seems to indicate the kernel32.lib error is related to 64bit building, but this is a 32bit build. :^(.

-kto