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 622526 - HAVE_INTROSPECTION does not appear in AM_CONDITIONAL
HAVE_INTROSPECTION does not appear in AM_CONDITIONAL
Status: RESOLVED FIXED
Product: anjuta
Classification: Applications
Component: libanjuta
git master
Other Linux
: High critical
: ---
Assigned To: Naba Kumar
Anjuta maintainers
: 633730 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-06-23 20:52 UTC by Massimo Cora'
Modified: 2013-06-18 13:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Massimo Cora' 2010-06-23 20:52:26 UTC
when running autogen.sh the following error occurs.


Running automake-1.11...
libanjuta/Makefile.am:214: HAVE_INTROSPECTION does not appear in AM_CONDITIONAL


There's need to add to configure.in the relative checks, but ATM I'm fixing symbol-db and I have no time for this one.
Comment 1 Sébastien Granjoux 2010-06-25 10:07:37 UTC
Do you think it's better to add a m4 directory and put introspection.m4 inside ?

Or just check for GOBJECT_INTROSPECTION_CHECK ?
m4_ifdef(GOBJECT_INTROSPECTION_CHECK, [GOBJECT_INTROSPECTION_CHECK([0.6.7])], AM_CONDITIONAL(HAVE_INTROSPECTION, false))
Comment 2 Naba Kumar 2010-06-27 09:14:47 UTC
(In reply to comment #1)
> Do you think it's better to add a m4 directory and put introspection.m4 inside
> ?
> 
> Or just check for GOBJECT_INTROSPECTION_CHECK ?
> m4_ifdef(GOBJECT_INTROSPECTION_CHECK, [GOBJECT_INTROSPECTION_CHECK([0.6.7])],
> AM_CONDITIONAL(HAVE_INTROSPECTION, false))

Does introspection support require more than just the macro? If yes, then later is more appropriate since just having the script would not be sufficient condition to enable it.

BTW, currently build fails without installing gobject-introspection, something needs to check for its presence before. I don't know if check for this macro gives sufficient clue, I guess not.
Comment 3 Sébastien Granjoux 2010-06-27 09:44:52 UTC
(In reply to comment #2)
> Does introspection support require more than just the macro?

Yes, basically this macro check for the package object-introspection-1.0 and defined several variable it finds it. The issue is that the macro comes with gobject-introspection package, so if it's not installed you cannot use the macro to check if it's installed.

> BTW, currently build fails without installing gobject-introspection, something
> needs to check for its presence before. I don't know if check for this macro
> gives sufficient clue, I guess not.

The line 'm4_ifdef...' check if the macro is present. And if it's present, the macro is used to check if introspection is supported. So I think that's fine.
Comment 4 Naba Kumar 2010-06-27 17:31:16 UTC
(In reply to comment #3)
> 
> The line 'm4_ifdef...' check if the macro is present. And if it's present, the
> macro is used to check if introspection is supported. So I think that's fine.

Then I guess checking for the macro is better.
Comment 5 Sébastien Granjoux 2010-06-27 19:06:01 UTC
I have committed the fix.
Comment 6 Andrés G. Aragoneses (IRC: knocte) 2013-06-18 13:15:59 UTC
*** Bug 633730 has been marked as a duplicate of this bug. ***
Comment 7 Andrés G. Aragoneses (IRC: knocte) 2013-06-18 13:18:10 UTC
(In reply to comment #5)
> I have committed the fix.

Just in case anyone from the duped bug is interested, the commit that solved this is: https://git.gnome.org/browse/anjuta/commit/?id=ec82284cc305aa6d2c3ebe85554bfe2aa40278bd