LDAP functionable? ldap.c does not compile on Solaris 2.6 /SWAT bug?

[Frans Stekelenburg]

Hi,

Is there anybody who succesfully compiled 2.0.4b INCLUDING LDAP support
"--with-ldap"? And on Solaris 2.6 (2.x)?

I first had configure run with also the NISPLUS option, but didn't want
that after all. I had a lot of problems trying to get Samba accepting
connections anyway.

That compiled oke: there's a little bug? in the SAMBA source somewhere
however, because I always get this line during compilation:

    ...
    Compiling lib/system.c
    lib/system.c: In function `sys_readdir':
    lib/system.c:338: warning: return from incompatible pointer type
    Compiling lib/doscalls.c
    ...


HOWEVER- then I tried to 'configure' and make solely with LDAP support.
Configure goes OK, and compiling to it as far as the message above but I
do NOT get further then:

    ...
    Compiling smbd/ssl.c
    mkdir bin
    Linking bin/smbd
    Undefined                       first referenced
     symbol                             in file
    ldap_initialize_password_db         passdb/passdb.o
    ld: fatal: Symbol referencing errors. No output written to bin/smbd
    gmake: *** [bin/smbd] Error 1


And that is that...!  ldap_initialize_password_db should come from
passdb/ldap.c though... so?



So seemingly the ldap.c doesn't get compiled/included after all..? Or is
there a overlooked inclusion left out?


I stripped all the 'optional' parts from 'configure' AND from ldap.c-
trying to FORCE a compilation, but then I got a load of source code
errors from ldap.c.
For instance a lot of  if statements contained   "  !  =  " ....  I got
rid of those messaged by replacing them with "!=".  No space in between.



How is LDAP implemented anyway?  We had have a 1.9.x LDAP 'hack' version
that runs oke, it picks up the uid/gid and homedirectory from LDAP as
well. Is that implemented in this ldap support?



SWAT


BTW. SWAT looks like a runaway train- it seemed to continuously fill my
syslog with the config parse lines

Jun 17 11:46:07 dev-snws-1.houten.acriter.nl swat[7506]:   doing
parameter ldap suffix = o=foo.com
Jun 17 11:46:07 dev-snws-1.houten.acriter.nl swat[7506]:   doing
parameter ldap filter = uid=%u
Jun 17 11:46:07 dev-snws-1.houten.acriter.nl swat[7506]:   doing
parameter NIS homedir = Yes
Jun 17 11:46:07 dev-snws-1.houten.acriter.nl swat[7507]:   doing
parameter log file = /var/adm/samba.log
Jun 17 11:46:07 dev-snws-1.houten.acriter.nl swat[7507]:   doing
parameter printcap name = /etc/printers.conf
Jun 17 11:46:07 dev-snws-1.houten.acriter.nl swat[7507]:   doing
parameter ldap server = ldap.bar.foo.com
Jun 17 11:46:07 dev-snws-1.houten.acriter.nl swat[7507]:   doing
parameter ldap suffix = o=foo.com
Jun 17 11:46:07 dev-snws-1.houten.acriter.nl swat[7507]:   doing
parameter ldap filter = uid=%u
Jun 17 11:46:07 dev-snws-1.houten.acriter.nl swat[7507]:   doing
parameter NIS homedir = Yes
Jun 17 11:46:07 dev-snws-1.houten.acriter.nl swat[7508]:   doing
parameter log file = /var/adm/samba.l....

continously etc etc..





Oh well, who can shed some light on this LDAP story?


Kinds regards,
Frans Stekelenburg