The generated-configure.sh script is dead, long live autoconf!
thomas.stuefe at gmail.com
Mon Feb 5 16:30:16 UTC 2018
On Mon, Feb 5, 2018 at 9:21 AM, Magnus Ihse Bursie <
magnus.ihse.bursie at oracle.com> wrote:
> <snip> With the new solution, the exact version of autoconf does not
> matter. <snip>
It seems to matter. I now get:
Using autoconf at /usr/bin/autoconf [autoconf (GNU Autoconf) 2.63]
stdin:33: error: Autoconf version 2.69 or higher is required
stdin:33: the top level
autom4te: /usr/bin/m4 failed with exit status: 63
Do we actually need this strict check for the autoconf version? Is there a
way to disable the check and retry with my old version?
I would dislike for this to be a frequent error now - unfortunately, we
have some build environments where getting the latest GNU tools is more
work than just running an installer.
> The build documentation has been updated to reflect this change.
More information about the jdk-dev