-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b04
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8208833 | 8u201 | Kevin Walls | P2 | Resolved | Fixed | b01 |
JDK-8201500 | 8u192 | Kevin Walls | P2 | Closed | Fixed | b01 |
JDK-8216633 | emb-8u201 | Kevin Walls | P2 | Resolved | Fixed | master |
This is a follow-up to JDK-8035495. It turned out that some of our internal systems where calling the configure wrapper (common/autoconf/configure) directly, instead of the top-level script.
This will change the wrapper so that such usage gets a warning, but not fail, giving those users time to transition to calling the top-level entry point instead.
This will change the wrapper so that such usage gets a warning, but not fail, giving those users time to transition to calling the top-level entry point instead.
- backported by
-
JDK-8208833 Warn instead of fail when calling the configure wrapper directly
-
- Resolved
-
-
JDK-8216633 Warn instead of fail when calling the configure wrapper directly
-
- Resolved
-
-
JDK-8201500 Warn instead of fail when calling the configure wrapper directly
-
- Closed
-
- relates to
-
JDK-8035495 Improvements in autoconf integration
-
- Resolved
-