On 2013-11-04 19:16, Rich P wrote:
Hello --
Are there any known issues with msvcr100.dll when building OpenJDK8 on Windows
8.1 Pro?
The msvcr100.dll is typically a source of problems when building OpenJDK
on Windows. :-)
We need to get hold of a version of msvcr100.dll which matches the
platform you are about to build. In Visual Studio, this is included for
32 and 64-bit. However, in Visual Studio Express, it is not included (at
all, as far as I know -- or perhaps only 32-bit).
Using the setup below, the configure script fails with the following
msvcr100.dll-related errors:
(1) configure: The file type of the located msvcr100.dll is PE32+ executable for MS Windows (DLL) (GUI) Mono/.Net assembly
That's a new one. Where did configure pick this one up?
(2) [Using the --with-msvcr-dll option] configure: The file type of the located
msvcr100.dll is PE32 executable for MS Windows (DLL) (GUI) Intel 80386 32-bit
This is the 32-bit version. I take it you are trying to build a 64-bit
target, since this was not accepted by configure.
There are several msvcr100.dll files on the build machine. The script can find
the msvcr100.dll in both Windows/System32 and the one in the Visual C++ x64
folder via the VS100COMNTOOLS variable. Explicitly pointing to a different one
(including the msvcr100.dll bundled with JDK 1.7) always produces one of the
above errors.
You can check the file type yourself of the different msvcr100.dll files
by using "file msvcr100.dll".
My setup:
Windows 8.1 Pro (64 bit)
JDK 1.7.0_45 (64 bit)
Microsoft Visual C++ 2010 Express (Version 10.0.30319.1 RTMRel)
Microsoft .NET Framework (Version 4.5.51641 RTMRel)
Microsoft Visual C++ 2010 x86 and x64 redistributables with SP1
Microsoft Visual C++ 2008 x86 and x64 redistributables with SP1
MinGW/MSYS (mingw-developer-toolkit, mingw32-base & msys-base versions
2013072300, mingw32-gcc-g++ version 4.8.1-4)
Aha, you're using msys! The recommended build environment on Windows is
cygwin. I didn't think msys was actually working at this point.
It might be the case that the msys "file" command classifies the dll
differently.
Can you post an excerpt of the output from configure when it tries to
find a working msvcr100.dll?
/Magnus
