[Q21.5] configure.in and ldap

Ilya> 2005-12-17 Ilya N. Golubev <gin(a)mo.msk.ru&gt; * configure.ac: Avoid inadvertent use of cached test results the same way as did in `configure.in' for autoconf 2.13. As an additional defense, use `$as_unset' from 2.59. I'm confused about code you've added in regard to caching. Why do we need $as_unset if AC_CACHE_VALUE is turned into the identity? Second, if we're not going to be using the cache, what are the AC_CACHE_CHECK calls for? Ilya> 2005-12-16 Ilya N. Golubev <gin(a)mo.msk.ru&gt; * configure.ac: Fixed `LDAP_OPT_ON' libraries configuration introduced in local 2004-12-20 change of `configure.in'. However, do not check for internal `-lber' `ber_pvt_opt_on' symbol as done in upstream. By "upstream", do you mean the prepatch XEmacs code, or OpenLDAP, or what? Ilya> 2004-12-20 Ilya N. Golubev <gin(a)mo.msk.ru&gt; * configure.in: Fix ldap libraries configuration lossage when `-lldap -llber' links and but `-lldap' does not; the lossage was introduced in revision 1.232. Also allow `ldap_libs' to be empty or overridden by builder. I don't understand the use case for ldap_libs being empty, or overridden. Also, how does the builder override ldap_libs? -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.