After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 621969 - [gnome-3.0] Problem building NetworkManager
[gnome-3.0] Problem building NetworkManager
Status: RESOLVED INVALID
Product: jhbuild
Classification: Infrastructure
Component: module sets
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Jhbuild maintainers
Jhbuild QA
Depends on:
Blocks:
 
 
Reported: 2010-06-18 08:56 UTC by Łukasz Jernaś
Modified: 2010-07-11 18:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Łukasz Jernaś 2010-06-18 08:56:16 UTC
When building NetworkManager from the 3.0 moduleset I get:
** Configuring NetworkManager *** [31/39]
./autogen.sh --prefix /opt/gnome2 --libdir '/opt/gnome2/lib64'  --disable-static --disable-gtk-doc 
configure.ac:64: warning: AM_NLS is m4_require'd but not m4_defun'd
/opt/gnome2/share/aclocal/intltool.m4:27: IT_PROG_INTLTOOL is expanded from...
configure.ac:64: the top level
configure.ac:64: warning: AM_NLS is m4_require'd but not m4_defun'd
aclocal.m4:458: IT_PROG_INTLTOOL is expanded from...
configure.ac:64: the top level
configure.ac:64: warning: AM_NLS is m4_require'd but not m4_defun'd
aclocal.m4:458: IT_PROG_INTLTOOL is expanded from...
configure.ac:64: the top level
configure.ac:20: error: possibly undefined macro: AC_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure:5526: error: possibly undefined macro: AM_NLS
autoreconf: /usr/bin/autoconf failed with exit status: 1

I've wiped the directory but it still persists.

I had to enter the shell and run gettextize and libtoolize manually
Comment 1 Frederic Peters 2010-06-18 09:06:55 UTC
Do you have nls.m4? (it should be installed by gettext)

Anyway I am closing this bug report, as jhbuild is not the place to discuss build failures in "random" modules (I kind of tolerate this for modules in official suites, but it's not possible to do it for the modules that are in gnome-3.0.modules). Traditionnaly the gnome-love mailing list has been used for build errors (and I am subscribed, and I read it).
Comment 2 Frank Solensky 2010-07-11 18:57:18 UTC
For the benefit of anyone else running into this issue: http://mail.gnome.org/archives/gnome-love/2010-July/msg00003.html