Re: STDCXX issue

[Vincent Blondel]

this is the run with warnings ...

$ autoreconf --verbose --force --install --warnings=all
autoreconf-2.69: Entering directory `.'
autoreconf-2.69: configure.ac: not using Gettext
autoreconf-2.69: running: aclocal --force --warnings=all ${ACLOCAL_FLAGS}
-I m4
autoreconf-2.69: configure.ac: tracing
configure.ac:13: warning: 'AM_CONFIG_HEADER': this macro is obsolete.
configure.ac:13: You should use the 'AC_CONFIG_HEADERS' macro instead.
aclocal.m4:730: AM_CONFIG_HEADER is expanded from...
configure.ac:13: the top level
configure.ac:23: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:23: You should run autoupdate.
m4/libtool.m4:99: AC_PROG_LIBTOOL is expanded from...
configure.ac:23: the top level
autoreconf-2.69: running: libtoolize --copy --force
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'
autoreconf-2.69: running: /usr/bin/autoconf-2.69 --force --warnings=all
configure.ac:13: warning: 'AM_CONFIG_HEADER': this macro is obsolete.
configure.ac:13: You should use the 'AC_CONFIG_HEADERS' macro instead.
aclocal.m4:730: AM_CONFIG_HEADER is expanded from...
configure.ac:13: the top level
configure.ac:23: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:23: You should run autoupdate.
m4/libtool.m4:99: AC_PROG_LIBTOOL is expanded from...
configure.ac:23: the top level
autoreconf-2.69: running: /usr/bin/autoheader-2.69 --force --warnings=all
autoreconf-2.69: running: automake --add-missing --copy --force-missing
--warnings=all
configure.ac:18: installing './compile'
configure.ac:14: installing './missing'
Makefile.am: installing './depcomp'
autoreconf-2.69: Leaving directory `.'

On Mon, Jan 20, 2020 at 2:47 PM Sébastien Hinderer <
address@hidden> wrote:

> Hi vincent,
>
> I'm all but an autoconf expert. Is it on purpose that you didn't call
> AC_INIT at the beginningof your autoconf script?
>
> Did you try running autoconf and automake with warnings enable to see
> whether they find something suspicious in your code?
>
> Best wishes,
>
> Sébastien.
>
>