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 564931 - autogen.sh should complain about gconf2-devel not being present, instead of lack of macro
autogen.sh should complain about gconf2-devel not being present, instead of l...
Status: RESOLVED DUPLICATE of bug 595495
Product: gnome-common
Classification: Core
Component: general
2.24.x
Other All
: Normal minor
: ---
Assigned To: Gnome Common Maintainer(s)
Gnome Common Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-12-17 22:38 UTC by Andrés G. Aragoneses (IRC: knocte)
Modified: 2009-10-12 16:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Andrés G. Aragoneses (IRC: knocte) 2008-12-17 22:38:49 UTC 
Please describe the problem:
Title says it all.

Steps to reproduce:
1. Run autogen.sh


Actual results:
Running autoconf...
configure.ac:225: error: possibly undefined macro: AM_GCONF_SOURCE_2
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.


Expected results:
Complain about gconf2-devel not being present.

Does this happen every time?
Yes.

Other information:
Workaround: install gconf2-devel.
Comment 1 Paolo Borelli 2009-01-02 11:11:40 UTC 
that's weird it should first complain when we do 

PKG_CHECK_MODULES(GEDIT, [
	libxml-2.0 >= 2.5.0
	glib-2.0 >= 2.18.0
	gthread-2.0 >= 2.13.0
	gio-2.0 >= 2.16.0
	gtk+-2.0 >= 2.13.0
	gtksourceview-2.0 >= 2.2.0
	gconf-2.0 >= 1.1.11
])

are you compiling an old version?


Apart from that I don't think there is much we can do...
Comment 2 Ignacio Casal Quinteiro (nacho) 2009-08-21 20:08:34 UTC 
Can you tell us if this is still happening to you? It shouldn't as paolo said we have the check for.
Comment 3 Christian Persch 2009-09-17 16:33:09 UTC 
Re comment 1: this happens when running autogen (aclocal phase probably), which is before configure runs and could complain about the missing gconf-2.0 pc file.

*If* we consider autogen complaining about "possibly undefined macro AM_GCONF_SOURCE_2" instead of saying "gconf devel not installed", it would be a bug in gnome-autogen.sh from gnome-common.
Comment 4 Andrés G. Aragoneses (IRC: knocte) 2009-10-12 16:14:07 UTC 
(In reply to comment #3)
> *If* we consider autogen complaining about "possibly undefined macro
> AM_GCONF_SOURCE_2" instead of saying "gconf devel not installed", it would be a
> bug in gnome-autogen.sh from gnome-common.

Ok, retargetting from gedit to gnome-common. Besides, I'm confirming the bug because now it happened to me when trying to compile a different gnome program: Banshee.

Is there any more info I could provide in order to help the resolution of this bug? Thanks!
Comment 5 Christian Persch 2009-10-12 16:19:54 UTC 

*** This bug has been marked as a duplicate of bug 595495 ***