public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin-apps@cygwin.com
Subject: pinfo build fails with undefined macro: AM_INTL_SUBDIR
Date: Tue, 11 Apr 2023 09:21:39 -0400	[thread overview]
Message-ID: <ogma3ils16vf4j7aduvniei09i9pr25ooq@4ax.com> (raw)

I'm trying to rebuild pinfo 0.6.13. That's the current version in Cygwin, so I
know I was able to build it successfully a couple of years ago. But now when I
try, the build fails with 

error: possibly undefined macro: AM_INTL_SUBDIR

I'm afraid my grasp of autotools is too weak for me to know what the problem is
here. At present I'm using the inherited src_complile() function from
autotools.cygclass. In the past I used:

src_compile ()
{
    cd "$S"
    gettextize -f   # needed to create tools/config.rpath
    cygautoreconf --install
    cd "$B"
    cygconf
    cygmake
}

but that doesn't fix the AM_INTL_SUBDIR problem.

The full build log is below. Could someone suggest a solution?

Thanks,
Andrew

$ cygport pinfo.cygport make
*** Warning: Building on a case-insensitive filesystem
>>> Compiling pinfo-0.6.13-3.x86_64
autoreconf-2.71: export WARNINGS=
autoreconf-2.71: Entering directory '.'
autoreconf-2.71: running: /usr/bin/autopoint -V 0.21.1 --force
autopoint: warning: Version mismatch: specified -V 0.21.1 but the package uses
gettext version 0.14.4. Forcibly upgrading to 0.21.1
autoreconf-2.71: running: aclocal --force -I macros
configure.ac:144: warning: macro 'AM_INTL_SUBDIR' not found in library
autoreconf-2.71: configure.ac: tracing
autoreconf-2.71: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'tools'.
libtoolize: copying file 'tools/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'macros'.
libtoolize: copying file 'macros/libtool.m4'
libtoolize: copying file 'macros/ltoptions.m4'
libtoolize: copying file 'macros/ltsugar.m4'
libtoolize: copying file 'macros/ltversion.m4'
libtoolize: copying file 'macros/lt~obsolete.m4'
autoreconf-2.71: configure.ac: not using Intltool
autoreconf-2.71: configure.ac: not using Gtkdoc
autoreconf-2.71: running: aclocal --force -I macros
configure.ac:144: warning: macro 'AM_INTL_SUBDIR' not found in library
autoreconf-2.71: running: /usr/bin/autoconf-2.71 --force
configure.ac:55: warning: The macro `AC_PROG_CC_C99' is obsolete.
configure.ac:55: You should run autoupdate.
/mnt/share/cygpkgs/autoconf2.7/autoconf2.7.noarch/src/autoconf-2.71/lib/autoconf/c.m4:1659:
AC_PROG_CC_C99 is expanded from...
configure.ac:55: the top level
configure.ac:104: warning: The macro `AC_CHECKING' is obsolete.
configure.ac:104: You should run autoupdate.
/mnt/share/cygpkgs/autoconf2.7/autoconf2.7.noarch/src/autoconf-2.71/lib/autoconf/general.m4:2499:
AC_CHECKING is expanded from...
macros/readline.m4:102: AC_SEARCH_READLINE is expanded from...
macros/readline.m4:46: AC_CHECK_READLINE is expanded from...
configure.ac:104: the top level
configure.ac:104: warning: The macro `AC_FD_CC' is obsolete.
configure.ac:104: You should run autoupdate.
/mnt/share/cygpkgs/autoconf2.7/autoconf2.7.noarch/src/autoconf-2.71/lib/autoconf/general.m4:399:
AC_FD_CC is expanded from...
macros/readline.m4:111: AC_READLINE_VERSION is expanded from...
macros/readline.m4:46: AC_CHECK_READLINE is expanded from...
configure.ac:104: the top level
configure.ac:159: error: possibly undefined macro: AM_INTL_SUBDIR
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf-2.71: error: /usr/bin/autoconf-2.71 failed with exit status: 1
*** ERROR: autoreconf failed


             reply	other threads:[~2023-04-11 13:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 13:21 Andrew Schulman [this message]
2023-04-11 14:32 ` Corinna Vinschen
2023-04-11 23:51   ` Andrew Schulman
2023-04-12  7:29     ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ogma3ils16vf4j7aduvniei09i9pr25ooq@4ax.com \
    --to=schulman.andrew@epa.gov \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).