I just updated my custom docker images to debian:bookworm, took a fresh clone from current master (ea6a40a2cbf05efb00f3418f2d0ad71232565beb) and I am getting the follownig error during build:
Step 8/17 : RUN /bin/sh autogen.sh
---> Running in ab4d6110f6d3
Running aclocal
Running libtoolize
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
Running automake --add-missing --copy
configure.ac:8: installing './ar-lib'
configure.ac:8: installing './compile'
configure.ac:9: installing './config.guess'
configure.ac:9: installing './config.sub'
configure.ac:5: installing './install-sh'
configure.ac:5: installing './missing'
Running autoconf
configure.ac:12: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:12: You should run autoupdate.
aclocal.m4:121: AC_PROG_LIBTOOL is expanded from...
configure.ac:12: the top level
configure.ac:58: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:58: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
./lib/autoconf/general.m4:1534: AC_ARG_ENABLE is expanded from...
configure.ac:58: the top level
All done.
To build the software now, do something like:
$ ./configure [...other options]
$ make
Configure complains about some macros beeing obsolete.
The build runs without problems after this, though.
Is this expected behaviour?
I just updated my custom docker images to
debian:bookworm, took a fresh clone from current master (ea6a40a2cbf05efb00f3418f2d0ad71232565beb) and I am getting the follownig error during build:Configure complains about some macros beeing obsolete. The build runs without problems after this, though. Is this expected behaviour?