Closed esabol closed 3 months ago
Bootstrap on Alpine 3.19 also works. It has autoconf 2.71-r2 and libtool 2.4.7-r3.
That would seem to imply the problem is with autoconf 2.72-r0?
https://lists.gnu.org/archive/html/bug-autoconf/2024-01/msg00012.html says this:
To work around the warning in autoconf-2.72, you can change the spelling of version.m4 to something functionally equivalent, for example:
m4_include([./version.m4])
You can also just go in and delete the indication that Autoconf uses to produce this warning, for example:
m4_builtin([undefine], [m4_include(version.m4)])
Incidentally, while not relevant to your example, Autoconf 2.72 also installs its own version.m4 file to the global m4 include search path, so if you were previously using M4PATH or autoconf's -I option to locate a file with this name then actually m4_include([version.m4]) will pick up the one shipped with Autoconf instead of what probably anyone would actually want to happen in this scenario.
m4_include([./version.m4])
seems to work well, and I think it should avoid the issue with the version.m4
file the autoconf/m4 maintainers have added to the global m4 include search path.
Fixed by PR #409. Closing.
Building on Alpine 3.20 fails at the bootstrap (libtoolize) stage:
https://github.com/gearman/gearmand/actions/runs/10027061889/job/27712225025?pr=362#step:10:32
Alpine 3.20.1 has autoconf 2.72-r0 and libtool 2.4.7-r3.
Bootstrap on Alpine 3.17 works. It has autoconf 2.71-r3 and libtool 2.4.7-r1.