The generated-configure.sh script is dead, long live autoconf! (original) (raw)

Thomas Stüfe thomas.stuefe at gmail.com
Mon Feb 5 16:53:50 UTC 2018

On Mon, Feb 5, 2018 at 5:46 PM, Martin Buchholz <martinrb at google.com> wrote:

In defense of build-team's decision, autoconf 2.69 was released in 2012, and it's possible to run autoconf on another machine than the build machine, and autoconf itself is easy to build.

If you can verify that your old version of autoconf works, then the version check in the sources can/should be relaxed.

Yes, until now I just ran autoconf on my local linux box. I will check if the older autoconf works.

..Thomas

On Mon, Feb 5, 2018 at 8:30 AM, Thomas Stüfe <thomas.stuefe at gmail.com> wrote:

Hi Magnus,

On Mon, Feb 5, 2018 at 9:21 AM, Magnus Ihse Bursie <_ _magnus.ihse.bursie at oracle.com> wrote:

> With the new solution, the exact version of autoconf does not > matter. > 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. Thanks, Thomas > > The build documentation has been updated to reflect this change. > > /Magnus > >

More information about the jdk-dev mailing list