Issues about build openj9 jdk on windows
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Build openj9 jdk11 on windows runs into the same issue hit by [build-openj9](https://github.com/eclipse/build-openj9)
```
TR_BUILD_NAME: aa9321e4f
J9SRC: D:\a\runaqa\runaqa\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm
JIT_SRCBASE: D:\a\runaqa\runaqa\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm
JIT_OBJBASE: D:\a\runaqa\runaqa\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm/objs
JIT_DLL_DIR: D:\a\runaqa\runaqa\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm
OMR_DIR: D:\a\runaqa\runaqa\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm/omr
BUILD_CONFIG: prod
NUMBER_OF_PROCESSORS: 2
VERSION_MAJOR: 11
Compiling 51 files for jdk.internal.opt
ENABLE_GPU: 1
CUDA_HOME: C:/progra~1/nvidia~2/cuda/v9.0
GDK_HOME: /NVIDIA/gdk
/usr/bin/make -j 2 -C D:\a\runaqa\runaqa\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm/compiler -f compiler.mk
make[6]: Entering directory '/cygdrive/d/a/runaqa/runaqa/openj9-openjdk-jdk11/build/windows-x86_64-normal-server-release/vm/compiler'
make[6]: warning: -j2 forced in submake: resetting jobserver mode.
if not exist "D:\a\runaqa\runaqa\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm\" mkdir "D:\a\runaqa\runaqa\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm\"
The filename, directory name, or volume label syntax is incorrect.
make[6]: *** [D:/a/runaqa/runaqa/openj9-openjdk-jdk11/build/windows-x86_64-normal-server-release/vm/compiler/build/rules/win-msvc/common.mk:90: jit_createdirs] Error 1
make[6]: Leaving directory '/cygdrive/d/a/runaqa/runaqa/openj9-openjdk-jdk11/build/windows-x86_64-normal-server-release/vm/compiler'
make[5]: *** [makefile:70: default] Error 2
```
the build scceeds if TR_BUILD_NAME=
```
TR_BUILD_NAME: 2ac59e97f
J9SRC: D:\a\runaqaTest\runaqaTest\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm
JIT_SRCBASE: D:\a\runaqaTest\runaqaTest\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm
JIT_OBJBASE: D:\a\runaqaTest\runaqaTest\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm/objs
JIT_DLL_DIR: D:\a\runaqaTest\runaqaTest\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm
OMR_DIR: D:\a\runaqaTest\runaqaTest\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm/omr
BUILD_CONFIG: prod
NUMBER_OF_PROCESSORS: 2
VERSION_MAJOR: 11
ENABLE_GPU: 1
CUDA_HOME: C:/progra~1/nvidia~2/cuda/v9.0
GDK_HOME: /NVIDIA/gdk
/usr/bin/make -j 2 -C D:\a\runaqaTest\runaqaTest\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm/compiler -f compiler.mk
make[6]: Entering directory '/cygdrive/d/a/runaqaTest/runaqaTest/openj9-openjdk-jdk11/build/windows-x86_64-normal-server-release/vm/compiler'
make[6]: warning: -j2 forced in submake: resetting jobserver mode.
if not exist "D:\a\runaqaTest\runaqaTest\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm\" mkdir "D:\a\runaqaTest\runaqaTest\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm\"
if not exist "D:\a\runaqaTest\runaqaTest\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm\objs\" mkdir "D:\a\runaqaTest\runaqaTest\openj9-openjdk-jdk11\build\windows-x86_64-normal-server-release\vm\objs\"
```
https://github.com/sophia-guo/runaqaTest/runs/714167242
https://github.com/sophia-guo/runaqa/runs/763406944?check_suite_focus=true
Contributor guide
Research direction
Start with the failing Windows JDK 11 build output and compare the successful and failing TR_BUILD_NAME paths. Inspect compiler/compiler.mk and build/rules/win-msvc/common.mk around line 90, then reproduce the mkdir failure using the linked GitHub Actions runs; done means the build succeeds with a non-empty TR_BUILD_NAME.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100