Bug 87297 - autoconf build error concerning undefined macros in configure.ac on ubuntu14.10
Summary: autoconf build error concerning undefined macros in configure.ac on ubuntu14.10
Status: RESOLVED NOTABUG
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-14 01:40 UTC by calebtillman
Modified: 2014-12-14 05:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description calebtillman 2014-12-14 01:40:51 UTC 
Ubuntu 14.04

$ autoconf

configure.ac:9: error: possibly undefined macro: AM_INIT_AUTOMAKE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:15: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
configure.ac:17: error: possibly undefined macro: AC_PROG_LIBTOOL
configure.ac:37: error: possibly undefined macro: AC_DEFINE
configure.ac:72: error: possibly undefined macro: AM_CONDITIONAL
configure.ac:102: error: possibly undefined macro: AC_MSG_ERROR
configure.ac:111: error: possibly undefined macro: AC_DEFINE_DIR
configure.ac:118: error: possibly undefined macro: AC_CHECK_HEADERS
configure.ac:133: error: possibly undefined macro: AC_CHECK_LIB
configure.ac:699: error: possibly undefined macro: AM_ICONV

------------------------

The fix is found at: https://bbs.archlinux.org/viewtopic.php?pid=1258673

$ sudo pacman -S pkg-config xorg-server-devel libtool automake
$ libtoolize --force

Consider adding AC_CONFIG_MACRO_DIR([m4]) to configure.ac
and re-run libtoolize --force.

$ vim configure.ac
$ libtoolize --force
$ aclocal
$ autoheader
$ automake --force-missing --add-missing
$ autoconf

I don't know how to include this in the build script.
Comment 1 Jason Crain 2014-12-14 05:25:42 UTC 
Don't run autoconf directly.  The way to build poppler with the autotools system is to use the autogen.sh script.  Or at least use 'autoreconf -i'.  It will run things in the right order.  It's not easy to know when to run aclocal, autoheader, libtoolize, automake, or autoconf.
Comment 2 calebtillman 2014-12-14 05:36:58 UTC 
Thanks, you're absolutely right. Sorry, I'm really new to the gnu toolchain.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.