Some additional point. I have checked - file
c:\openJdk\openjdk8u\build\windows-x86_64-normal-server-release\hotspot\windows_amd64_compiler2\product\ad_x86_64_peephole.obj
exists. So I am quite entangled here If object was built and exists -
why linker fails to add it to a library?
чт, 11 июл.
Looks like you are using a newer Visual Studio toolchain:
'C:\PROGRA~2\MICROS~1\2017\PROFES~1\VC\Tools\MSVC\14.16.27023\
See below:
On 07/11/19 12:35, Moshe Zuisman wrote:
now I pulled last source (used get_ssource.sh) and - same result:
[...snip...]
*Generating Code...sh
C:\openJ
now I pulled last source (used get_ssource.sh) and - same result:
*Generating Code...sh
C:\openJdk8u_test\jdk8u\hotspot/make/windows/build_vm_def.sh
C:\progra~2\micros~1\2017\profes~1\vc\tools\msvc\1416~1.270\bin\hostx86\x64\link.exe
@C:\cygwin64\tmp\nmE8BD.tmp Creating li
Sorry - it is b04
But if get you right - i will have to last commit...
$ hg log --rev $(hg id -i | sed 's/.$//')
changeset: 2369:d43cf567cf72
tag: jdk8u212-b04
user:andrew
date:Wed Apr 03 05:14:53 2019 +0100
summary: Added tag jdk8u212-b03 for changeset 5218ef8ea6c3
On 7/11/19 1:17 PM, Moshe Zuisman wrote:
> I am trying to build openjdk8u_b24 on windows cygwin environment.
What is "openjdk8u_b24"? What exactly are you trying to build? In other words,
where did you get the
source, and what is the latest change in the source tree? There are many
improvements
