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 596660 - configure script contains an automagic support
configure script contains an automagic support
Status: RESOLVED OBSOLETE
Product: libgweather
Classification: Core
Component: general
2.26.x
Other Linux
: Normal normal
: 2.22.0
Assigned To: libgweather-maint
libgweather-maint
Depends on:
Blocks:
 
 
Reported: 2009-09-28 20:01 UTC by Romain Perier
Modified: 2012-03-05 16:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch which solves the problem (838 bytes, patch)
2009-09-28 20:01 UTC, Romain Perier
none Details | Review

Description Romain Perier 2009-09-28 20:01:55 UTC
Created attachment 144195 [details] [review]
patch which solves the problem

Hey,

due to the following code :
AC_ARG_ENABLE(python,
        [AC_HELP_STRING([--enable-python],
                        [Build libgweather python bindings])],
        [enable_python=yes],
        [enable_python=no])

That's impossible to disable python support if --disable-support is given on
the command line.
We use a function called "use_enable" in ebuilds (on gentoo), which returns
"--enable-foo" if "foo" support is activated (in USE-flags) or "--disable-foo"
if "foo" is disabled.
The user is finally able to set/uset an optionnal supports dynamically.

This problem is a bit annoying, because when python support is disabled in
USE-flags, python dependencies aren't pulled in the graph dep, so the
compilation fails.

Now have a look at http://www.gentoo.org/proj/en/qa/automagic.xml to understand
in more details why automagic is so bad.

You will find in attachment a patch to fix this issue.
This upstream refers to downstream bug https://bugs.gentoo.org/285595.

Romain.
Comment 1 Javier Jardón (IRC: jjardon) 2012-03-05 16:45:36 UTC
This bug is not valid anymore, we use GObject introspection bindings now