-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 11, 17, 21
-
Component/s: infrastructure
-
b05
-
generic
-
windows
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8300393 | 20.0.1 | Sergey Bylokhov | P3 | Resolved | Fixed | b02 |
| JDK-8300165 | 20 | Sergey Bylokhov | P3 | Resolved | Fixed | b32 |
| JDK-8300175 | 17.0.7 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
| JDK-8300174 | 11.0.19 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
This causes build to fail if the runtime libraries are located in different dirs and passed by related options to the configure.
- backported by
-
JDK-8300165 Compilation of gtest causes build to fail if runtime libraries are in different dirs
-
- Resolved
-
-
JDK-8300174 Compilation of gtest causes build to fail if runtime libraries are in different dirs
-
- Resolved
-
-
JDK-8300175 Compilation of gtest causes build to fail if runtime libraries are in different dirs
-
- Resolved
-
-
JDK-8300393 Compilation of gtest causes build to fail if runtime libraries are in different dirs
-
- Resolved
-
- links to
-
Commit
openjdk/jdk11u-dev/7bbb6ba0
-
Commit
openjdk/jdk17u-dev/1032a0f0
-
Commit
openjdk/jdk20/e15bdc58
-
Commit
openjdk/jdk/c8a8388a
-
Review
openjdk/jdk11u-dev/1644
-
Review
openjdk/jdk17u-dev/1051
-
Review
openjdk/jdk20/94
-
Review
openjdk/jdk/11899