Re: file locking, 2.4.1 vs. 2.4.2

2001-02-23 Thread Alexandre Oliva
On Feb 20, 2001, "John R. Jackson" [EMAIL PROTECTED] wrote: Also, someone has added this test to the main branch, but it's very odd: pushdef([AC_DEFINE_SAVED],defn([AC_DEFINE])) pushdef([AC_DEFINE],[AC_DEFINE_SAVED([$1],[$2],[Define to $2 if $1 is not defined])]) AC_CHECK_TYPE(ssize_t, int)

Re: file locking, 2.4.1 vs. 2.4.2

2001-02-20 Thread Alexandre Oliva
On Feb 20, 2001, "John R. Jackson" [EMAIL PROTECTED] wrote: This appears to be caused by someone getting a little too enthusiastic with ssize_t (signed size type), which apparently your OS does not provide, at least in the normal include files. It would probably be sufficient to add

file locking, 2.4.1 vs. 2.4.2

2001-02-19 Thread Mario Obejas
On an Auspex, SunOS caeauspex 4.1.4 1 AUSPEX-VERSION 1.9.2M1Z2 aushp When running configure for 2.4.2p1, I get: checking whether posix fcntl locking works... no checking whether flock locking works... no checking whether lockf locking works... no checking whether lnlock locking works... no

Re: file locking, 2.4.1 vs. 2.4.2

2001-02-19 Thread John R. Jackson
Here's your answer, hope it's not too much: It was just what I needed. In file included from common-src/amflock.c:48, from configure:19266: common-src/amanda.h:509: parse error before `areads_dataready' ... This appears to be caused by someone getting a little too enthusiastic