-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b131
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8208844 | 8u201 | Alexey Ivanov | P2 | Resolved | Fixed | b01 |
| JDK-8204171 | 8u192 | Alexey Ivanov | P2 | Closed | Fixed | b01 |
| JDK-8216644 | emb-8u201 | Alexey Ivanov | P2 | Resolved | Fixed | master |
Sometimes the detected CL.EXE cannot be run without additions to the PATH in configure. This seems to happen with certain VS2010 and VS2012 installations.
The error appears as:
configure: error: Target CPU mismatch. We are building for x86 but CL is for "directory"; expected "80x86" or "x86".
The best solution seems to be to move the check in TOOLCHAIN_MISC_CHECKS to closer to where we locate the compiler, and still have the VS PATH setup.
The error appears as:
configure: error: Target CPU mismatch. We are building for x86 but CL is for "directory"; expected "80x86" or "x86".
The best solution seems to be to move the check in TOOLCHAIN_MISC_CHECKS to closer to where we locate the compiler, and still have the VS PATH setup.
- backported by
-
JDK-8208844 Fix broken CL version detection in configure for some Visual Studio configurations
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-