On Jan 04 10:17:08, s...@spacehopper.org wrote:
> That comes from iconv.m4 in gettext-tools. IIRC it only needs to be
> installed and you don't need to do anything special to tell automake to find
> it.
Yes, that was it - thank you.
While here:
$ env AUTOCONF_VERSION=2.71 AUTOMAKE_VERSION=1.16 autoreconf -v
autoreconf-2.71: export WARNINGS=
autoreconf-2.71: Entering directory '.'
autoreconf-2.71: configure.ac: not using Gettext
[...]
Apparently, autoreconf _is_ using gettext (namely, gettext's iconv.m4
to parse th AM_ICONV macro), so what does 'not using Gettext' mean?
Thanks again,
Jan
> --
> Sent from a phone, apologies for poor formatting.
>
> On 4 January 2023 07:52:55 Jan Stary <h...@stare.cz> wrote:
>
> > Some third party software, e.g. wavpack, uses AM_ICONV
> > in its configure.ac when building from git.
> >
> > (I know we have a port that already comes with ./configure,
> > so this problem does not occur there.)
> >
> > I do have automake and the rest installed,
> > but autogen.sh complains that
> >
> > autoreconf-2.71: export WARNINGS=
> > autoreconf-2.71: Entering directory '.'
> > autoreconf-2.71: configure.ac: not using Gettext
> > autoreconf-2.71: running: aclocal
> > configure.ac:66: warning: macro 'AM_ICONV' not found in library
> >
> > Please excuse my ignorance: I know next to nothing about the auto* hell.
> > I do have libiconv installed, as well as the following:
> >
> > autoconf-2.69p3
> > autoconf-2.71
> > autoconf-archive-2022.09.03
> > autogen-5.8.7p7
> > automake-1.16.5
> > metaauto-1.0p4
> >
> > Is there something else I need to have
> > so that the AM_ICONV macro is recognized,
> > like the other AM_* stuff in configure.ac?
> >
> > Thank you,
> >
> > Jan
>
>
