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 646444 - configuring with --enable-gdu
configuring with --enable-gdu
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: build
1.6.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2011-04-01 14:23 UTC by Michael Wood
Modified: 2018-05-04 10:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Wood 2011-04-01 14:23:18 UTC 
configuring with --enable-gdu doesn't cause configure to bail out if gdu is missing. 

I had a look at the configure.ac in master and it doesn't look different so i'm guessing this is still a bug.
Comment 1 Felix Möller 2012-08-01 20:37:57 UTC 
Thanks for your report.

This applies to every module used as far as I can see.

It can be solved by:
fm@thinkpad:~/tmp/gvfs$ git diff
diff --git a/configure.ac b/configure.ac
index 2bcbebb..f46a73e 100644
--- a/configure.ac
+++ b/configure.ac
@@ -208,7 +208,7 @@ GDU_CFLAGS=
 GDU_REQUIRED=3.0.2
 
 if test "x$enable_gdu" != "xno"; then
-  PKG_CHECK_EXISTS([gdu >= $GDU_REQUIRED], msg_gdu=yes)
+  PKG_CHECK_EXISTS([gdu >= $GDU_REQUIRED], msg_gdu=yes, AC_MSG_ERROR([Could not find GDU.]))
 
   if test "x$msg_gdu" = "xyes"; then
     PKG_CHECK_MODULES([GDU],[gdu >= $GDU_REQUIRED])


However, I am not sure if this is wanted...
Comment 2 Ondrej Holy 2018-05-04 10:12:41 UTC 
This is an old bug and autotools and gdu support were already removed. Let's close as obsolete.