jdk9 client windows build problem

[Magnus Ihse Bursie]

On 2015-02-25 11:25, prasanta sadhukhan wrote:
> Hi,
>
> I am trying to build jdk9 client workspace ( 
> http://hg.openjdk.java.net/jdk9/client).
> I installed Visual C++ 2010 express and I could see VS100COMNTOOLS 
> env. var has been setup. But when I try to configure, i am getting 
> following problem. Does anyone know what might cause this?
>
> $ bash ./configure --with-target-bits=32
> Running custom generated-configure.sh
> configure: Configuration created at Wed Feb 25 14:41:14 IST 2015.
> configure: configure script generated at timestamp 1424202275.
> checking for basename... /usr/bin/basename
> checking for bash... /usr/bin/bash
> checking for cat... /usr/bin/cat
> checking for chmod... /usr/bin/chmod
> checking for cmp... /usr/bin/cmp
> checking for comm... /usr/bin/comm
> checking for cp... /usr/bin/cp
> checking for cut... /usr/bin/cut
> checking for date... /usr/bin/date
> checking for gdiff... no
> checking for diff... /usr/bin/diff
> checking for dirname... /usr/bin/dirname
> checking for echo... /usr/bin/echo
> checking for expr... /usr/bin/expr
> checking for file... /usr/bin/file
> checking for find... /usr/bin/find
> checking for head... /usr/bin/head
> checking for ln... /usr/bin/ln
> checking for ls... /usr/bin/ls
> checking for mkdir... /usr/bin/mkdir
> checking for mktemp... /usr/bin/mktemp
> checking for mv... /usr/bin/mv
> checking for nawk... no
> checking for gawk... /usr/bin/gawk
> checking for printf... /usr/bin/printf
> checking for rm... /usr/bin/rm
> checking for sh... /usr/bin/sh
> checking for sort... /usr/bin/sort
> checking for tail... /usr/bin/tail
> checking for tar... /usr/bin/tar
> checking for tee... /usr/bin/tee
> checking for touch... /usr/bin/touch
> checking for tr... /usr/bin/tr
> checking for uname... /usr/bin/uname
> checking for uniq... /usr/bin/uniq
> checking for wc... /usr/bin/wc
> checking for which... /usr/bin/which
> checking for xargs... /usr/bin/xargs
> checking for gawk... gawk
> checking for grep that handles long lines and -e... /usr/bin/grep
> checking for egrep... /usr/bin/grep -E
> checking for fgrep... /usr/bin/grep -F
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for cygpath... /usr/bin/cygpath
> checking for greadlink... no
> checking for readlink... /usr/bin/readlink
> checking for df... /usr/bin/df
> checking for SetFile... no
> checking for cpio... /usr/bin/cpio
> checking build system type... x86_64-pc-cygwin
> checking host system type... x86_64-pc-cygwin
> checking target system type... x86_64-pc-cygwin
> checking openjdk-build os-cpu... windows-x86_64
> checking openjdk-target os-cpu... windows-x86_64
> checking compilation type... reduced
> checking cygwin release... 1.7.17(0.262/5/3)
> checking cygwin root directory as unix-style path... /cygdrive/c/cygwin
> checking what kind of 'find' is first on the PATH... unix style
> checking for top-level directory... /cygdrive/c/jdk9/client
> checking for presence of closed sources... yes
> checking if closed source is suppressed (openjdk-only)... no
> checking which variant of the JDK to build... normal
> checking which interpreter of the JVM to build... template
> checking which variants of the JVM to build... server
> checking which debug level to use... release
> checking for parfait... not enabled
> checking for sysroot...
> checking for toolchain path...
> checking for extra path...
> checking where to store configuration... in default location
> checking what configuration name to use... 
> windows-x86-normal-server-release
> checking for apt-get... no
> checking for yum... no
> checking for port... no
> checking for pkgutil... no
> checking for pkgadd... no
> checking for gmake... no
> checking for make... /usr/bin/make
> configure: Testing potential make at /usr/bin/make, found using make 
> in PATH
> configure: Using GNU make 3.81 (or later) at /usr/bin/make (version: 
> GNU Make 3.82.90)
> checking if make --output-sync is supported... no
> checking if find supports -delete... yes
> checking for unzip... /usr/bin/unzip
> checking for zip... /usr/bin/zip
> checking for ldd... /usr/bin/ldd
> checking for otool... no
> checking for greadelf... no
> checking for readelf... /usr/bin/readelf
> checking for hg... /usr/bin/hg
> checking for stat... /usr/bin/stat
> checking for time... no
> checking if bash supports pipefail... yes
> checking if bash supports errexit (-e)... yes
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for 7z... no
> checking for unzip... unzip
> checking for wget... no
> checking for lftp... no
> checking for ftp... ftp
> checking headful support... include support for both headful and headless
> checking for javac... /cygdrive/c/jdk1.8.0_31/bin/javac
> checking for java... /cygdrive/c/jdk1.8.0_31/bin/java
> configure: Found potential Boot JDK using java(c) in PATH
> checking for Boot JDK... /cygdrive/c/jdk1.8.0_31
> checking Boot JDK version... java version "1.8.0_31"  Java(TM) SE 
> Runtime Environment (build 1.8.0_31-b13)  Java HotSpot(TM) Client VM 
> (build 25.31-b07, mixed mode)
> checking for java in Boot JDK... ok
> checking for javac in Boot JDK... ok
> checking for javah in Boot JDK... ok
> checking for jar in Boot JDK... ok
> checking for native2ascii in Boot JDK... ok
> checking for jarsigner in Boot JDK... ok
> configure: Using default toolchain microsoft (Microsoft Visual Studio)
> checking for link... /usr/bin/link
> checking if the first found link.exe is actually the Cygwin link 
> tool... yes
> configure: Found Visual Studio installation at /cygdrive/c/Program 
> Files (x86)/Microsoft Visual Studio 10.0/ using VS100COMNTOOLS variable
> configure: Found Microsoft Visual Studio 2010
> configure: Rewriting VS_ENV_CMD to 
> "/cygdrive/c/progra~2/micros~1.0/vc/bin/vcvars32.bat"
> configure: Trying to extract Visual Studio environment variables
> Setting environment for using Microsoft Visual Studio 2010 x86 tools.
> configure: Setting extracted environment variables
> checking for Visual Studio variables... ok
> configure: Rewriting ipath to 
> "/cygdrive/c/progra~2/micros~1.0/vc/include"
> configure: Rewriting ipath to 
> "/cygdrive/c/progra~2/mia713~1/windows/v7.0a/include"
> configure: Rewriting libpath to "/cygdrive/c/progra~2/micros~1.0/vc/lib"
> configure: Rewriting libpath to 
> "/cygdrive/c/progra~2/mia713~1/windows/v7.0a/lib"
> checking for cl... /cygdrive/c/Program Files (x86)/Microsoft Visual 
> Studio 10.0/VC/BIN/cl
> configure: Rewriting CC to "/cygdrive/c/progra~2/micros~1.0/vc/bin/cl"
> checking resolved symbolic links for CC... 
> /cygdrive/c/progra~2/micros~1.0/vc/bin/cl
> checking if CC is disguised ccache... no, keeping CC
> configure: Using microsoft C compiler version 16.00.30319.01 
> [Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.30319.01 
> for 80x86]
> checking whether the C compiler works... yes
> checking for C compiler default output file name... conftest.exe
> checking for suffix of executables... .exe
> checking whether we are cross compiling... no
> checking for suffix of object files... obj
> checking whether we are using the GNU C compiler... no
> checking whether /cygdrive/c/progra~2/micros~1.0/vc/bin/cl accepts 
> -g... yes
> checking for /cygdrive/c/progra~2/micros~1.0/vc/bin/cl option to 
> accept ISO C89... none needed
> checking for cl... /cygdrive/c/Program Files (x86)/Microsoft Visual 
> Studio 10.0/VC/BIN/cl
> configure: Rewriting CXX to "/cygdrive/c/progra~2/micros~1.0/vc/bin/cl"
> checking resolved symbolic links for CXX... 
> /cygdrive/c/progra~2/micros~1.0/vc/bin/cl
> checking if CXX is disguised ccache... no, keeping CXX
> configure: Using microsoft C++ compiler version 16.00.30319.01 
> [Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.30319.01 
> for 80x86]
> checking whether we are using the GNU C++ compiler... no
> checking whether /cygdrive/c/progra~2/micros~1.0/vc/bin/cl accepts 
> -g... yes
> checking how to run the C preprocessor... 
> /cygdrive/c/progra~2/micros~1.0/vc/bin/cl -E
> checking how to run the C++ preprocessor... 
> /cygdrive/c/progra~2/micros~1.0/vc/bin/cl -E
> checking for link... link
> configure: Rewriting LD to "/cygdrive/c/progra~2/micros~1.0/vc/bin/link"
> checking if the found link.exe is actually the Visual Studio linker... 
> yes
> checking for lib... lib
> configure: Rewriting AR to "/cygdrive/c/progra~2/micros~1.0/vc/bin/lib"
> checking for mt... mt
> configure: Rewriting MT to 
> "/cygdrive/c/progra~2/mia713~1/windows/v7.0a/bin/mt"
> checking for rc... rc
> configure: Rewriting RC to 
> "/cygdrive/c/progra~2/mia713~1/windows/v7.0a/bin/rc"
> checking for dumpbin... dumpbin
> configure: Rewriting DUMPBIN to 
> "/cygdrive/c/progra~2/micros~1.0/vc/bin/dumpbin"
> checking for msbuild.exe... msbuild.exe
> checking for gobjdump... no
> checking for objdump... objdump
> configure: Rewriting OBJDUMP to "/usr/bin/objdump"
> checking for jtreg... no
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... no
> checking for inttypes.h... no
> checking for stdint.h... yes
> checking for unistd.h... no
> checking stdio.h usability... yes
> checking stdio.h presence... yes
> checking for stdio.h... yes
> checking size of int *... 4
> checking for target address size... 32 bits
> checking whether byte ordering is bigendian... no
> checking if compiler supports "-m32"... yes
> checking if compiler supports "-m32"... yes
> checking if we should generate debug symbols... true
> checking if we should zip debug-info files... yes
> checking if fixpath can be created... yes
> checking if fixpath.exe works... yes
> checking what is not needed on Windows?... alsa cups pulse x11
> checking for which libjpeg to use... bundled
> checking for which giflib to use... bundled
> checking for which lcms to use... bundled
> checking for which libpng to use... bundled
> checking for compress in -lz... no
> checking for which zlib to use... bundled
> checking for cos in -lm... yes
> checking for dlopen in -ldl... no
> POSSIBLE_MSVC_DLL
> configure: Found msvcr100.dll at 
> /cygdrive/c/jdk1.8.0_31/bin/msvcr100.dll using well-known location in 
> Boot JDK
> checking found msvcr100.dll architecture... ok
> checking for msvcr100.dll... /cygdrive/c/jdk1.8.0_31/bin/msvcr100.dll
> checking if elliptic curve crypto implementation is present... yes
> checking for number of cores... 4
> checking for memory size... 8097 MB
> checking for appropriate number of jobs to run in parallel... 4
> checking flags for boot jdk java command ...
> checking flags for boot jdk java command for big workloads... -Xms64M 
> -XX:ThreadStackSize=1536
> checking flags for boot jdk java command for small workloads... 
> -XX:+UseSerialGC -Xms32M -Xmx512M
> configure: WARNING: Could not set -Xms256M -Xmx1500M, disabling sjavac
> checking whether to use sjavac... no
> checking is ccache enabled... no
> checking if build directory is on local disk... yes
> checking Checking for deploy src... not found, cannot build deploy
> checking Checking for install src... not found, cannot build installer
> checking for ant... no
> configure: Ant is needed for deploy, set 
> --with-ant-home=/path/to/ant-home
> checking for JUnit... no, deploy tests cannot be run
> checking for wix... no, needed for installer, set --with-wix=/path/to/wix
> checking for lzma... no, needed for installer, set 
> --with-lzma-path=/path/to/lzma
> checking for UPX... no, needed for installer
> no, needed for installer
> checking for wscript... /cygdrive/c/windows/system32/wscript
> checking for cscript... /cygdrive/c/windows/system32/cscript
> checking for msicert... no
> cygpath: can't convert empty path
> cygpath: can't convert empty path
> configure: The path of MSICERT, which resolves as "", is not found.
> configure: error: Cannot locate the the path of MSICERT
> configure exiting with result code 1
>
> $ echo $VS100COMNTOOLS
> C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\

You are missing msicert (which is only used in Oracle closed builds), 
but that should not be a fatal error. There is indeed a bug in the 
configure script which does not handle this properly. I filed 
JDK-8073862, will fix it shortly.

/Magnus