diff options
author | Irfan Adilovic <i.adilovic@nfotex.com> | 2016-04-17 22:05:15 +0200 |
---|---|---|
committer | Daniel Stenberg <daniel@haxx.se> | 2016-04-21 23:08:28 +0200 |
commit | d9f3b365a3b663d6e45ff734a86b313e2fbcbbf2 (patch) | |
tree | 18cc55e54d13894a1ad6daf8e0825f7b86bbb0f1 /lib/version.c | |
parent | 4b639dbc747e69b2e017d1e1b8b2a9beb4711bfd (diff) |
configure: ac_cv_ -> curl_cv_ for write-only vars
These configure vars are modified in a curl-specific way but never
evaluated or loaded from cache, even though they are designated as
_cv_. We could either implement proper AC_CACHE_CHECKs for them, or
remove them completely.
Fixes #603 as ac_cv_func_gethostbyname is no longer clobbered, and
AC_CHECK_FUNC(gethostbyname...) will no longer spuriously succeed after
the first configure run with caching.
`ac_cv_func_strcasecmp` is curious, see #770.
`eval "ac_cv_func_$func=yes"` can still cause problems as it works in
tandem with AC_CHECK_FUNCS and then potentially modifies its result. It
would be best to rewrite this test to use a new CURL_CHECK_FUNCS macro,
which works the same as AC_CHECK_FUNCS but relies on caching the values
of curl_cv_func_* variables, without modifiying ac_cv_func_*.
Diffstat (limited to 'lib/version.c')
0 files changed, 0 insertions, 0 deletions