On Wed, Nov 07, 2012 at 06:54:46AM -0800, Murray S. Kucherawy wrote:
> Actually, if you have libstrl already installed, you should be able to
> provide CPPFLAGS, LDFLAGS and LIBS options to ./configure that discover
> this, which would prevent our package from building and installing our
> libstrl. Have you tried this?
No, I assumed they were different. In any case, a proper configure
check is probably preferable. A quick hack with the patch below seems
to work for me on Linux but I am getting test failures when linked
against libstrl.so library (from the libstrl package) - did not
investigate any longer.
--- configure.ac 2012-10-30 18:12:46.000000000 +0000
+++ configure.ac 2012-11-07 18:47:39.047786180 +0000
_at_@ -181,8 +181,10 @@
AC_CHECK_FUNCS([dup2 endpwent getcwd gethostname gethostbyname getaddrinfo gethostbyname2 gettimeofday isascii memchr memmove memset regcomp select socket strcasecmp strchr strdup strerror strncasecmp strrchr strstr strtol strtoul strtoull])
strl_found="no"
-AC_CHECK_FUNCS([strlcat strlcpy], [strl_found="yes"], [strl_found="no"])
-AM_CONDITIONAL([STRL], [test x"$strl_found" != x"yes"])
+libstrl_found="no"
+AC_CHECK_FUNCS([strlcat], [strl_found="yes"],
+ [AC_SEARCH_LIBS([strlcat], [strl], [libstrl_found="yes"], [strl_found="no"])])
+AM_CONDITIONAL([STRL], [test x"$strl_found" != x"yes" -a x"$libstrl_found" != x"yes"])
if test x"$strl_found" = x"yes"
then
AC_DEFINE([HAVE_STRL], 1,
--
Eray
Received on Wed Nov 07 2012 - 20:50:07 PST