GNOME Bugzilla – Bug 509630
gnome-vfs cannot be built if gssapi/gssapi_generic.h found in include path
Last modified: 2008-11-16 12:09:26 UTC
Please describe the problem: If gssapi/gssapi_generic.h is found in the include path (e.g. /usr/include) and there's a newer version (e.g. from heimdal 1.0.1) installed somewhere else, gnomve-vfs build fails with: In file included from ne_auth.c:66: /usr/include/gssapi/gssapi_generic.h:46: error: syntax error before 'extern' /usr/include/gssapi/gssapi_generic.h:47: error: syntax error before 'extern' /usr/include/gssapi/gssapi_generic.h:48: error: syntax error before 'extern' /usr/include/gssapi/gssapi_generic.h:50: error: syntax error before 'extern' Steps to reproduce: 1. Build gnome-vfs with --enable-ipv6 --enable-howl --disable-gnutls, where the above conditions are met. Actual results: Expected results: Does this happen every time? yes Other information: Platform: Mac OS X 10.4.11 (PPC). Note that gssapi/gssapi_generic.h cannot be removed since it is provided by the vendor. The configure script should check path consistency and/or disable gssapi/gssapi_generic.h if some problem is detected with it. Indeed, I get: [...] configure: GSSAPI authentication support enabled checking gssapi/gssapi_generic.h usability... no checking gssapi/gssapi_generic.h presence... yes configure: WARNING: gssapi/gssapi_generic.h: present but cannot be compiled configure: WARNING: gssapi/gssapi_generic.h: check for missing prerequisite headers? configure: WARNING: gssapi/gssapi_generic.h: see the Autoconf documentation configure: WARNING: gssapi/gssapi_generic.h: section "Present But Cannot Be Compiled" configure: WARNING: gssapi/gssapi_generic.h: proceeding with the preprocessor's result configure: WARNING: gssapi/gssapi_generic.h: in the future, the compiler will take precedence checking for gssapi/gssapi_generic.h... yes [...] So, I wonder why it is enabled...
Is this still a valid issue in gnome-vfs 2.24? Also note that gnome-vfs has been deprecated and superseded by gio/gvfs since GNOME 2.22.
The problem no longer occurs with MacPorts since heimdal is no longer installed in default paths (as it introduced clashes with other ports -- but this wasn't the same problem, AFAIK). So, I'm closing the bug as WONTFIX.