author | Florian Forster <octo@leeloo.lan.home.verplant.org> | |
Thu, 23 Apr 2009 09:10:26 +0000 (11:10 +0200) | ||
committer | Florian Forster <octo@leeloo.lan.home.verplant.org> | |
Thu, 23 Apr 2009 09:10:26 +0000 (11:10 +0200) | ||
commit | bcd6151b05ee67e7b916bfa575a25b751585a4f8 | |
tree | 621908789fb06f83724cf48b181aee9d04830833 | tree | snapshot |
parent | d04c883b1114f903022e8d772bc2c21db9af329a | commit | diff |
configure.in, network plugin: Use all tests to decide about gcrypt support.
On Doug's OpenBSD machine I've seen:
configure: gcrypt CPPFLAGS: -I/usr/local/include -I/usr/local/include
checking gcrypt.h usability... yes
checking gcrypt.h presence... yes
checking for gcrypt.h... yes
configure: gcrypt LDFLAGS: -L/usr/local/lib
checking for gcry_md_hash_buffer in -lgcrypt... no
Because so far the network plugin only used the existence of the header
file to determine whether or not to enable `gcrypt' support, the build
fails. With this patch, the plugin will use a define that's only
available if *all* tests were successful.
On Doug's OpenBSD machine I've seen:
configure: gcrypt CPPFLAGS: -I/usr/local/include -I/usr/local/include
checking gcrypt.h usability... yes
checking gcrypt.h presence... yes
checking for gcrypt.h... yes
configure: gcrypt LDFLAGS: -L/usr/local/lib
checking for gcry_md_hash_buffer in -lgcrypt... no
Because so far the network plugin only used the existence of the header
file to determine whether or not to enable `gcrypt' support, the build
fails. With this patch, the plugin will use a define that's only
available if *all* tests were successful.
configure.in | diff | blob | history | |
src/network.c | diff | blob | history |