samba - Sep 2000 - errors from ./configure

Hello-

I am getting the following errors from ./configure.  Any ideas on how to
remedy this?

.
.
.
checking for fcntl locking... no
checking for broken (glibc2.1/x86) 64 bit fcntl locking... no
checking for 64 bit fcntl locking... no
checking for sysv ipc... yes
checking for IRIX sysv ipc semun problem using gcc... no
checking for a crypt that needs truncated salt... no
checking for broken nisplus include files... yes
checking whether to use smbwrapper... no
checking whether to use AFS... no
checking whether to use DFS auth... no
checking whether to use Kerberos IV... no
checking whether to use Kerberos 5... no
checking whether to use AUTOMOUNT... no
checking whether to use SMBMOUNT... no
checking whether to use PAM password database... no
checking whether to use LDAP password database... no
checking whether to use NISPLUS password database... no
checking whether to use NISPLUS_HOME... no
checking whether to use SSL... no
checking whether to use syslog logging... no
checking whether to use profiling... no
checking whether to support netatalk... no
checking whether to support disk-quotas... no
checking whether to support utmp accounting... no
checking whether to install Using Samba book...
${prefix}/swat/using_samba
checking how to get filesystem space usage
checking statvfs64 function (SVR4)... no
checking statvfs function (SVR4)... yes
checking if large file support can be enabled
no
checking configure summary
ERROR: No locking available. Running Samba would be unsafe


Thanks,
Peter Bouton

On Mon, 25 Sep 2000, Peter Bouton wrote:
> Hello-
> 
> I am getting the following errors from ./configure.  Any ideas on how to
> remedy this?
Not really, because you are not supplying any info about your system ...
> checking if large file support can be enabled
> no
> checking configure summary
> ERROR: No locking available. Running Samba would be unsafe
... but one way to get that message is if you are running linux and do not
have the right kernel headers in /usr/include/{linux,asm} (usually a
symlink to /usr/src/linux).

Check your config.log what configure is failing on.

/Urban

On Mon, 25 Sep 2000, Urban Widmark wrote:
> On Mon, 25 Sep 2000, Peter Bouton wrote:
>
> > ERROR: No locking available. Running Samba would be unsafe
> 
> ... but one way to get that message is if you are running linux and do not
> have the right kernel headers in /usr/include/{linux,asm} (usually a
> symlink to /usr/src/linux).
A couple of other things that sometimes trip this warning:

1. Some platforms appear to need you to be root when running configure,
   whereas many admins do the "./configure; make" part of the process
as
   a normal user and only su to root for "make install". Try
re-running
   ./configure as root.

2. Sometimes this is seen if the Samba source tree is on an NFS file
   system and NFS locking isn't working properly (in which case the
   warning is valid if (and only if) you plan to use Samba to serve up
   files that you obtain via NFS (which is a silly idea - put Samba on
   the NFS server, rather than the NFS client)).

   If the source tree is on NFS, but you *don't* plan to re-export NFS
   filesystems using Samba, then move the Samba source tree to a local
   filesystem and try re-running ./configure.

Regards,
-- 
Neil Hoggarth                                 Departmental Computer Officer
<neil.hoggarth@physiol.ox.ac.uk>                   Laboratory of
Physiology
http://www.physiol.ox.ac.uk/~njh/                  University of Oxford, UK