1 - do better when cross-compiling when checking for strerror_r() - alert

the user.
2 - don't check for POSIX-style if glibc-style is found first
This commit is contained in:
Daniel Stenberg 2004-06-04 19:01:58 +00:00
parent e99d1e97de
commit e0b436f8e1
1 changed files with 9 additions and 2 deletions

View File

@ -423,10 +423,11 @@ main () {
return 0;
}
],
dnl if it worked fine
AC_DEFINE(HAVE_GLIBC_STRERROR_R, 1, [we have a glibc-style strerror_r()])
AC_MSG_RESULT([yes]),
dnl this didn't work!
AC_MSG_RESULT([no])
)
AC_MSG_CHECKING([for a POSIX strerror_r API])
AC_TRY_RUN([
@ -444,11 +445,17 @@ main () {
return 0;
}
],
dnl it worked, we have POSIX-style strerror()
AC_DEFINE(HAVE_POSIX_STRERROR_R, 1, [we have a POSIX-style strerror_r()])
AC_MSG_RESULT([yes]),
dnl it failed, we don't have POSIX-style
AC_MSG_RESULT([no])
)
) dnl end of AC_TRY_RUN() for POSIX strerror_r()
dnl cross-compiling!
,
AC_MSG_NOTICE([cannot determine strerror_r() style: edit lib/config.h manually!])
) dnl end of AC_TRY_RUN() for glibc strerror_r()
fi
])