This problem was discussed upstream, here:
http://bugzilla.gnome.org/show_bug.cgi?id=341942

And was fixed with this clean and simple patch to configure.in:
http://bugzilla.gnome.org/attachment.cgi?id=65572

The patch submitted by James is ok, but adds a lot of noise, because it
adds many other things to the configure script.

I managed to create a much smaller patch by running the old autoconf
instead of the new one.  I'm attaching the cleaned up patch, and I intent
to prepare an NMU with it  (will send another mail with the complete NMU
diff).

-- 
 Bessos,    (o_
    Marga.  (\)_
--- gnopernicus-untouched/configure     2006-08-23 18:38:34.223147389 -0300
+++ gnopernicus-1.0.5/configure 2006-08-23 18:42:33.444413335 -0300
@@ -23891,18 +23891,21 @@
     { (echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"\\
                  cspi-1.0 >= \$CSPI_REQUIRED \\
                  gconf-2.0 >= \$GCONF_REQUIRED \\
-                 glib-2.0 >= \$GLIB_REQUIRED \"") >&5
+                 glib-2.0 >= \$GLIB_REQUIRED
+                 gdk-2.0 >= \$GTK_REQUIRED \"") >&5
   ($PKG_CONFIG --exists --print-errors "\
                  cspi-1.0 >= $CSPI_REQUIRED \
                  gconf-2.0 >= $GCONF_REQUIRED \
-                 glib-2.0 >= $GLIB_REQUIRED ") 2>&5
+                 glib-2.0 >= $GLIB_REQUIRED
+                 gdk-2.0 >= $GTK_REQUIRED ") 2>&5
   ac_status=$?
   echo "$as_me:$LINENO: \$? = $ac_status" >&5
   (exit $ac_status); }; then
   pkg_cv_LIBKE_CFLAGS=`$PKG_CONFIG --cflags "\
                  cspi-1.0 >= $CSPI_REQUIRED \
                  gconf-2.0 >= $GCONF_REQUIRED \
-                 glib-2.0 >= $GLIB_REQUIRED " 2>/dev/null`
+                 glib-2.0 >= $GLIB_REQUIRED
+                 gdk-2.0 >= $GTK_REQUIRED " 2>/dev/null`
 else
   pkg_failed=yes
 fi
@@ -23914,18 +23917,21 @@
     { (echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"\\
                  cspi-1.0 >= \$CSPI_REQUIRED \\
                  gconf-2.0 >= \$GCONF_REQUIRED \\
-                 glib-2.0 >= \$GLIB_REQUIRED \"") >&5
+                 glib-2.0 >= \$GLIB_REQUIRED
+                 gdk-2.0 >= \$GTK_REQUIRED \"") >&5
   ($PKG_CONFIG --exists --print-errors "\
                  cspi-1.0 >= $CSPI_REQUIRED \
                  gconf-2.0 >= $GCONF_REQUIRED \
-                 glib-2.0 >= $GLIB_REQUIRED ") 2>&5
+                 glib-2.0 >= $GLIB_REQUIRED
+                 gdk-2.0 >= $GTK_REQUIRED ") 2>&5
   ac_status=$?
   echo "$as_me:$LINENO: \$? = $ac_status" >&5
   (exit $ac_status); }; then
   pkg_cv_LIBKE_LIBS=`$PKG_CONFIG --libs "\
                  cspi-1.0 >= $CSPI_REQUIRED \
                  gconf-2.0 >= $GCONF_REQUIRED \
-                 glib-2.0 >= $GLIB_REQUIRED " 2>/dev/null`
+                 glib-2.0 >= $GLIB_REQUIRED
+                 gdk-2.0 >= $GTK_REQUIRED " 2>/dev/null`
 else
   pkg_failed=yes
 fi
@@ -23937,14 +23943,16 @@
        LIBKE_PKG_ERRORS=`$PKG_CONFIG --errors-to-stdout --print-errors "\
                  cspi-1.0 >= $CSPI_REQUIRED \
                  gconf-2.0 >= $GCONF_REQUIRED \
-                 glib-2.0 >= $GLIB_REQUIRED "`
+                 glib-2.0 >= $GLIB_REQUIRED
+                 gdk-2.0 >= $GTK_REQUIRED "`
        # Put the nasty error message in config.log where it belongs
        echo "$LIBKE_PKG_ERRORS" 1>&5
 
        { { echo "$as_me:$LINENO: error: Package requirements (\
                  cspi-1.0 >= $CSPI_REQUIRED \
                  gconf-2.0 >= $GCONF_REQUIRED \
-                 glib-2.0 >= $GLIB_REQUIRED ) were not met.
+                 glib-2.0 >= $GLIB_REQUIRED
+                 gdk-2.0 >= $GTK_REQUIRED ) were not met.
 Consider adjusting the PKG_CONFIG_PATH environment variable if you
 installed software in a non-standard prefix.
 
@@ -23954,7 +23962,8 @@
 echo "$as_me: error: Package requirements (\
                  cspi-1.0 >= $CSPI_REQUIRED \
                  gconf-2.0 >= $GCONF_REQUIRED \
-                 glib-2.0 >= $GLIB_REQUIRED ) were not met.
+                 glib-2.0 >= $GLIB_REQUIRED
+                 gdk-2.0 >= $GTK_REQUIRED ) were not met.
 Consider adjusting the PKG_CONFIG_PATH environment variable if you
 installed software in a non-standard prefix.
 

Reply via email to