Hi Magnus,
Thx. I installed Cygwin and was able to successfully configure and build the
32 bit OpenJDK!
The successful configure command for me was:
./configure --with-target-bits=32
--with-msvcr-dll=/cygdrive/c/windows/syswow64/msvcr100.dll
--with-freetype="/cygdrive/c/program files (x86)/GNUWin32"
The 64 bit build failed with a message about "Target CPU mismatch" but I found
this issue which appears to be related
(http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8019229) and so I'll take a
look at that.
Thanks again - I appreciate all the help!
Rich
Date: Wed, 6 Nov 2013 15:54:57 +0100
From: magnus.ihse.bur...@oracle.com
To: tempbo...@hotmail.com
CC: build-dev@openjdk.java.net
Subject: Re: Building OpenJDK 8 on Windows 8.1 Pro -- problems with msvcr100.dll
On 2013-11-05 17:37, Rich P wrote:
After updating toolchain_windows.m4 as you suggest above
and re-running "bash ./configure", the script stops with the
message:
Configure source code has been updated, checking time stamps
Running generated-configure.sh
I pulled a fresh copy of the sources and tried again and
the script will not run after I modify toolchain_windows.m4.
Perhaps modifying the file (and thus the file's timestamp) is
preventing the configure script from running. Does the script
check file timestamps? If so, is there an easy way to get
around this?
The actual configure script that you run is generated (think
"compiled") from the source m4 files. For this, you need to have
autoconf. Unfortunately, last I checked, msys do not include
autoconf. :-( This means that you need to use cygwin, or another
operating system, to run autoconf. You will need at least autoconf
2.69, and preferrably exactly 2.69.
The way around that is to manually hack generated_configure.sh with
the same replacement as you did in the source file (use search in a
text editor to find it). I believe that will be enough to go around
the checks, when you use only the open parts. Otherwise you need to
hack around the checks as well, which is more tricky.
/Magnus
