GNOME Bugzilla – Bug 587709
Require explicit --disable-ssl to build without GNUTLS support -- Breaks Build
Last modified: 2009-10-13 16:27:59 UTC
Steps to reproduce: 1. configure 2. 3. Stack trace: Other information: The "fix": Author: Dan Winship <danw@gnome.org> Date: Sun Jun 28 10:00:00 2009 -0400 Require explicit --disable-ssl to build without GNUTLS support In general, if someone is trying to build without GNUTLS installed it's an accident, so bail out with an error. Inspired by http://bugzilla.gnome.org/show_bug.cgi?id=584955 in git master breaks the build. I get: checking for LIBGNUTLS... yes configure: error: Could not configure SSL support. Pass "--disable-ssl" if you really want to build without SSL support make: *** [configure-work/main.d/libsoup-git/configure] Error 1 I have recent versions of openssl and gnutls. This worked before the commit
hm... it looks like this will happen if you have gnutls-devel installed, but *don't* have libgcrypt-devel installed. Right? (In which case it would previously have just silently dropped ssl support, but now it actually fails.)
Actually I have both installed. Initially I didn't but had built/installed the most recent before filing the bug report.
Please attach config.log
Created attachment 137877 [details] config.log: configure log file As requested, here's configure's log file.
Hi Dan, I hate to be a pest, but not being able to upgrade libsoup has started to affect other parts of gnome (most recently, epiphinay via webkitgtk+-1.1.11 (which needs libsoup > 2.27.4) Any progress?
Created attachment 138342 [details] Terminal log of configure/build process.
Created attachment 138345 [details] config.log that goes with the output in Comment #6
*** Bug 596088 has been marked as a duplicate of this bug. ***
the last config.log still shows that it's being autogened without AM_PATH_LIBGCRYPT being found
I've just reinstalled libgcrypt (version 1.4.4) and gnutls (2.8.4). They built and tested fine, although libgcrypt doesn't seem to install a .pc file; rather prefix/bin/libcrypt-config is used. I flamed the git sources for libsoup and started from scratch (autogen/configure/make). Same error. What's weird is that greping config.log and/or configure for GCRYPT (case insensitive) finds nothing.
One final observation, forcing have_ssl=yes in configure gets around the problem (of course), and the resulting lib builds without complaint
We now include libgcrypt.m4 in the libsoup sources, so it will fail correctly if gnutls-devel is installed but libgcrypt-devel is not