GNOME Bugzilla – Bug 641651
configure should honor aclocal flags ACLOCAL_FLAGS
Last modified: 2011-02-07 10:10:08 UTC
I'm building empathy via JHBuild. empathy builds successfully. If upstream then updates configure.ac, then I run 'make', which attempts a reconfigure, but fails. This is because JHBuild sets ACLOCAL_FLAGS to include the sandbox (e.g. -I /opt/gnome/share/aclocal). One may argue it is silly for JHBuild to require every module to support ACLOCAL_FLAGS, but there isn't a way around it until automake-1.12 is out - which includes support for ACLOCAL_PATH. Further details in the JHBuild bug 634617. The build failure is: make V=1 CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /home/Oxyde/gnome/empathy/missing --run aclocal-1.11 -I m4 configure.ac:84: warning: macro `AM_PATH_GLIB_2_0' not found in library configure.ac:202: warning: macro `AM_GLIB_GNU_GETTEXT' not found in library configure.ac:22: warning: AC_INIT: not a literal: http://bugzilla.gnome.org/browse.cgi?product=empathy cd . && /bin/sh /home/Oxyde/gnome/empathy/missing --run automake-1.11 --gnu configure.ac:22: warning: AC_INIT: not a literal: http://bugzilla.gnome.org/browse.cgi?product=empathy CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /home/Oxyde/gnome/empathy/missing --run autoconf configure.ac:22: warning: AC_INIT: not a literal: http://bugzilla.gnome.org/browse.cgi?product=empathy configure.ac:84: error: possibly undefined macro: AM_PATH_GLIB_2_0 If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:202: error: possibly undefined macro: AM_GLIB_GNU_GETTEXT make: *** [configure] Error 1
Created attachment 180211 [details] [review] Honor aclocal flags
Like Ryan wrote in bug 634617 I think the solution is to wait for automake 1.12, not to go and patch every GNOME modules.
Agreed; let's fix this properly.
(In reply to comment #2) > Like Ryan wrote in bug 634617 I think the solution is to wait for automake > 1.12, not to go and patch every GNOME modules. Yes, automake 1.12 is the way to go but... I think this is an unobtrusive patch that solves an annoying problem in JHBuild. One day JHBuild works fine, the next day it does not - and this frustrated me. The above error provided little clues to the problem and I was glad when I finally tracked the problem down. It took me a long time to solve. I want JHBuild to work first time, every time and helps towards my goal.