On Fri, 19 Jan 2024 14:14:46 GMT, Magnus Ihse Bursie <i...@openjdk.org> wrote:
> In contrast with Erik I'm not so worried about future breakage. Autoconf has > basically stalled in development since decades. If someone were to pick up > development again (like what happened with GNU Make) we will surely see signs > of activity long before this breaks. And if that happens, we can just file a > bug on autoconf instead of trying to work around the broken behaviour, right? > 🤷 If you are ok with this, then I am too, just wanted to be thorough with possible concerns. I would just like to point out that it was a change in autoconf behavior that triggered this whole ordeal in the first place, so saying nothing is happening doesn't exactly seem true. The way I see it, if they change one of the sub/internal macros in an incompatible way, then we will just have to keep inlining the old versions of such macros in our configure script to work around it. I still think it would be prudent to verify this patch with all the currently accepted versions of autoconf (2.69, 2.70, 2.71, 2.72). ------------- PR Comment: https://git.openjdk.org/jdk/pull/17401#issuecomment-1901126832
