Currently, infrastructure/db/config.site holds these openpty(3)-related
values:
ac_cv_func_openpty=${ac_cv_func_openpty=no}
ac_cv_lib_util_openpty=${ac_cv_lib_util_openpty=yes}
At first glance, this makes sense. We have openpty() in libutil,
but not in libc. However, I'm already looking at the second port
today that does something like this:
AC_CHECK_LIB(util, openpty)
AC_CHECK_FUNCS(openpty)
This is a quite reasonable use of the available autoconf macros.
Check that libutil holds openpty, then check for openpty itself
with LIBS=-lutil. Unfortunately, our preloaded cache values cause
this to fail:
checking for openpty in -lutil... (cached) yes
checking for openpty... (cached) no
I move that we delete ac_cv_func_openpty from config.site.
Anybody have a suggestions for a pithy comment we can put in there
so ac_cv_func_openpty won't accidentally be included again?
--
Christian "naddy" Weisgerber na...@mips.inka.de
