Re: file locking, 2.4.1 vs. 2.4.2

[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)
 popdef([AC_DEFINE])
 popdef([AC_DEFINE_SAVED])

 Why is all that pushdef/popdef stuff in there?

Oh, now I remember!

The problem is that we don't have an acconfig.h template since we
moved all define templates into the third argument of AC_DEFINE.
However, AC_CHECK_TYPE calls AC_DEFINE without such an argument, so
autoheader would complain about no template being available for
ssize_t.  This was the ugly work-around I had come up with.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

Re: file locking, 2.4.1 vs. 2.4.2

[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

AC_CHECK_TYPE (ssize_t, int)

in configure.in, right after we check for size_t.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

file locking, 2.4.1 vs. 2.4.2

[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
configure: warning: *** No working file locking capability found!
configure: warning: *** Be VERY VERY careful.

When running configure for 2.4.1p1, I get:
checking whether posix fcntl locking works... yes

Same machine, same terminal window, different distribution directory.

Did the test for file locking change?

My configure command for the respective cases above:

./configure --with-user=root --with-group=bin \
  --prefix=/home/amanda/common --exec-prefix=/home/amanda_2.4.2
  
./configure --with-user=root --with-group=bin \
  --prefix=/home/amanda/common --exec-prefix=/home/amanda_2.4.1


Mario Obejas
Engineering Automation  Computing
Raytheon Electronic Systems
310-334-7201 (Voice)
310-366-4867 (Pager)

Re: file locking, 2.4.1 vs. 2.4.2

[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
with ssize_t (signed size type), which apparently your OS does not
provide, at least in the normal include files.

Please give the following patch a try.  There is still (deliberately)
one ssize_t left, so if your OS just plain doesn't have that defined,
it may fail when it comes to building this (it will happen in file.c)
but I think the patch will at least get you through ./configure.  If you
have more trouble, let me know and I'll add to the fix.

Mario Obejas

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

 file.diff