618 |
i370-ibm-aix*) |
i370-ibm-aix*) |
619 |
machine=ibm370aix opsys=usg5-3 |
machine=ibm370aix opsys=usg5-3 |
620 |
;; |
;; |
621 |
s390-*-linux-gnu) |
s390-*-linux-gnu* ) |
622 |
machine=ibms390 opsys=gnu-linux |
machine=ibms390 opsys=gnu-linux |
623 |
;; |
;; |
624 |
rs6000-ibm-aix3.1* | powerpc-ibm-aix3.1* ) |
rs6000-ibm-aix3.1* | powerpc-ibm-aix3.1* ) |
2198 |
# On HPUX 9.01, -lm does not contain logb, so check for sqrt. |
# On HPUX 9.01, -lm does not contain logb, so check for sqrt. |
2199 |
AC_CHECK_LIB(m, sqrt) |
AC_CHECK_LIB(m, sqrt) |
2200 |
|
|
2201 |
# Check for mail-locking functions in a "mail" library |
# Check for mail-locking functions in a "mail" library. Probably this should |
2202 |
|
# have the same check as for liblockfile below. |
2203 |
AC_CHECK_LIB(mail, maillock) |
AC_CHECK_LIB(mail, maillock) |
2204 |
dnl Debian, at least: |
dnl Debian, at least: |
|
dnl AC_CHECK_LIB(lockfile, maillock, [AC_DEFINE(HAVE_LIBMAIL)]) |
|
2205 |
AC_CHECK_LIB(lockfile, maillock) |
AC_CHECK_LIB(lockfile, maillock) |
2206 |
# If we have the shared liblockfile, assume we must use it for mail |
# If we have the shared liblockfile, assume we must use it for mail |
2207 |
# locking (e.g. Debian). If we couldn't link against liblockfile |
# locking (e.g. Debian). If we couldn't link against liblockfile |
2215 |
AC_MSG_ERROR([Shared liblockfile found but can't link against it. |
AC_MSG_ERROR([Shared liblockfile found but can't link against it. |
2216 |
This probably means that movemail could lose mail. |
This probably means that movemail could lose mail. |
2217 |
There may be a `development' package to install containing liblockfile.]) |
There may be a `development' package to install containing liblockfile.]) |
|
else AC_DEFINE(LIBMAIL, -llockfile, [Define to -llockfile if it is usable.]) |
|
|
fi |
|
2218 |
else : |
else : |
2219 |
|
fi |
2220 |
fi |
fi |
2221 |
AC_CHECK_FUNCS(touchlock) |
AC_CHECK_FUNCS(touchlock) |
2222 |
AC_CHECK_HEADERS(maillock.h) |
AC_CHECK_HEADERS(maillock.h) |
2482 |
|
|
2483 |
dnl Fixme: AC_SYS_POSIX_TERMIOS should probably be used, but it's not clear |
dnl Fixme: AC_SYS_POSIX_TERMIOS should probably be used, but it's not clear |
2484 |
dnl how the tty code is related to POSIX and/or other versions of termios. |
dnl how the tty code is related to POSIX and/or other versions of termios. |
2485 |
|
dnl The following looks like a useful start. |
2486 |
|
dnl |
2487 |
|
dnl AC_SYS_POSIX_TERMIOS |
2488 |
|
dnl if test $ac_cv_sys_posix_termios = yes; then |
2489 |
|
dnl AC_DEFINE(HAVE_TERMIOS, 1, [Define to 1 if you have POSIX-style functions |
2490 |
|
dnl and macros for terminal control.]) |
2491 |
|
dnl AC_DEFINE(HAVE_TCATTR, 1, [Define to 1 if you have tcgetattr and tcsetattr.]) |
2492 |
|
dnl fi |
2493 |
|
|
2494 |
dnl Fixme: Use AC_FUNC_MEMCMP since memcmp is used. (Needs libobj replacement.) |
dnl Fixme: Use AC_FUNC_MEMCMP since memcmp is used. (Needs libobj replacement.) |
2495 |
|
|