[Samba] configure incorrectly assumes my linux system is 64 bit capable

[Thomas Hannan]

Hi all, 

I've dug into a problem I've been having with Samba-3.0.0 (trying out
3.0.1 right now) on a linux system (2.4.18-3 kernel) with glibc 2.2.5
... when I run a ./configure (with or without --with-spinlocks) it tests
out my fcntl.h, and it fails the first fcntl.h test, the following one
(where it tests for a broken glibc 2.1), but then passes the 64 bit
fcntl test!? Now when it compiles, and I run it, almost any windows app
that opens a file on a share (with or without oplocks enabled) generates
errors

Jan 27 16:12:32 gw-uk smbd[17710]: [2004/01/27 16:12:32, 0]
locking/posix.c:posix_fcntl_lock(656)
Jan 27 16:12:32 gw-uk smbd[17710]:   posix_fcntl_lock: WARNING: lock
request at offset 1010, length 2 returned
Jan 27 16:12:32 gw-uk smbd[17710]: [2004/01/27 16:12:32, 0]
locking/posix.c:posix_fcntl_lock(658)
Jan 27 16:12:32 gw-uk smbd[17710]:   an No locks available error. This
can happen when using 64 bit lock offsets
Jan 27 16:12:32 gw-uk smbd[17710]: [2004/01/27 16:12:32, 0]
locking/posix.c:posix_fcntl_lock(659)
Jan 27 16:12:32 gw-uk smbd[17710]:   on 32 bit NFS mounted file systems.

How do I keep samba from trying to pass a 64 bit lock request down to
the POSIX subsystem? It seems that this used to be the default behavior
in the samba 2.2.x series, because I haven't had this problem on my old
samba 2.2.5 systems.

Anyone?
thanks in advance,
Thomas