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,
>It would probably be sufficient to add
>
>AC_CHECK_TYPE (ssize_t, int)
>
>in configure.in, right after we check for size_t.
You would think so. But the code was actually wrong (not terribly,
but the references I changed were unsigned so size_t would be fine),
and sending a patch out for ./confi
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
AC_
>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 enthusia
Here's your answer, hope it's not too much:
>> Mario Obejas <[EMAIL PROTECTED]> wrote
>cc: [EMAIL PROTECTED]
>Subject: Re: file locking, 2.4.1 vs. 2.4.2
>Date: Mon, 19 Feb 2001 17:44:54 -0500
>From: "John R. Jackson" <[EMAIL PROTECTED]>
>When running configure for 2.4.2p1, I get:
>checking whether posix fcntl locking works... no
>...
>When running configure for 2.4.1p1, I get:
>checking whether posix fcntl locking works... yes
>...
>Did the test for file locking change?
It's possible. What's in config.log for the failin
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
