[Samba] samba & solaris 8

Eric Boehm boehm at nortelnetworks.com
Mon Feb 25 10:08:04 GMT 2002

On Mon, Feb 25, 2002 at 10:59:17AM -0500, John Dalton wrote:
>>>>> "John" == John Dalton <jldalton at lucent.com> writes:

    John> trying to compile 2.2.3a on solaris 8 and getting the
    John> following:

    John> Is it supported on sol 8?

I've had no problem building any version of Samba on Solaris (2.6, 7,

    John> after typing configure and after many lines i get:

-----much deleted------
ecking how to get filesystem space usage
checking statvfs64 function (SVR4)... no
checking statvfs function (SVR4)... no
checking for 3-argument statfs function (DEC OSF/1)... no
checking for two-argument statfs with statfs.bsize member (AIX, 4.3BSD)... no
checking for four-argument statfs (AIX-3.2.5, SVR3)... no
checking for two-argument statfs with statfs.fsize member (4.4BSD and NetBSD)...
checking for two-argument statfs with struct fs_data (Ultrix)... no
checking if large file support can be enabled... no
checking whether to support ACLs... no
checking whether to build winbind... no, no unix domain socket support on
checking configure summary
ERROR: No locking available. Running Samba would be unsafe
configure: error: summary failure. Aborting config

You might want to look at config.log for the details on what is
actually going wrong. The message about no unix domain socket support
is very strange. What compiler are you using? Is there anything funny
in your PATH. Do you have any LD*PATH variables set?

Try the following. I am assuming you are using Bourne/Korn Shell. If
you are using C-shell or a derivative, replace "unset" with
"unsetenv", use "set path=( dir dir dir )" instead of PATH=, use ">&"
instead of "> file 2>&1". Use setenv CONFIG_SHELL ...

1. Open new window. 

2. Set a minimal PATH, e.g.,

   If your compiler is in a different directory, add that to your PATH

3. Unset and LD*PATH variables, e.g.,
   unset LD_OPTIONS
   unset LD_RUN_PATH
   unset LD_LIBRARY_PATH_64

4. Re-run configure. If it still fails, look at config.log so you can
   see what is wrong. If that still doesn't work, run configure like

   CONFIG_SHELL='/usr/bin/ksh -x'
   export CONFIG_SHELL
   ${CONFIG_SHELL} ./configure > config.out 2>&1

   Then find your problems in config.log and correlate them with
   output in config.out

5. If you are still stumped you can post a reply with information from
   config.log and config.out
Eric M. Boehm                  /"\  ASCII Ribbon Campaign
boehm at nortelnetworks.com       \ /  No HTML or RTF in mail
                                X   No proprietary word-processing
Respect Open Standards         / \  files in mail

More information about the samba mailing list