-
Bug
-
Resolution: Fixed
-
P3
-
11.0.17, 17.0.5, 20
-
b19
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8300191 | 17.0.7 | Severin Gehwolf | P3 | Resolved | Fixed | b01 |
JDK-8295784 | 15.0.10 | Yuri Nesterenko | P3 | Resolved | Fixed | b01 |
JDK-8300293 | 11.0.19 | Severin Gehwolf | P3 | Resolved | Fixed | b01 |
It is not clear to me why they consider this to be a problem, but the warning is printed whenever you run configure with autoconf 2.71 or newer, and it is annoying.
We're only doing this in one place. Let's hardcode the values instead so we get rid of the warning.
- backported by
-
JDK-8295784 Fix autoconf 2.71 warning "AC_CHECK_HEADERS: you should use literals"
-
- Resolved
-
-
JDK-8300191 Fix autoconf 2.71 warning "AC_CHECK_HEADERS: you should use literals"
-
- Resolved
-
-
JDK-8300293 Fix autoconf 2.71 warning "AC_CHECK_HEADERS: you should use literals"
-
- Resolved
-
- duplicates
-
JDK-8273145 Autoconf 2.71 prints warning when generating runnable configure script
-
- Closed
-
-
JDK-8294581 AC_CHECK_HEADERS warning with autoconf 2.71
-
- Closed
-
- links to
-
Commit openjdk/jdk11u-dev/edf4fb0a
-
Commit openjdk/jdk15u-dev/489dd4f1
-
Commit openjdk/jdk17u-dev/7043b63b
-
Commit openjdk/jdk/c357b590
-
Review openjdk/jdk11u-dev/1653
-
Review openjdk/jdk15u-dev/291
-
Review openjdk/jdk17u-dev/1066
-
Review openjdk/jdk/10672