Bug 6846 - Configure fail on 64 bit mode with ADS, OpenLDAP not compatible ?
Configure fail on 64 bit mode with ADS, OpenLDAP not compatible ?
Status: RESOLVED FIXED
Product: Samba 3.2
Classification: Unclassified
Component: Build environment
3.2.7
Sparc Solaris
: P3 normal
: ---
Assigned To: Björn Jacke
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-26 10:04 UTC by Eric PLANCHE
Modified: 2009-11-07 15:16 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric PLANCHE 2009-10-26 10:04:36 UTC
Attempting to compile Samba 3.2.7 on Solaris 8 & 10 Sparc with latest patches bundle, in 64 bits mode with Active Directory, ldap and Kerberos.

On Solaris 10, flags are following: 
LDFLAGS=-L/usr/sfw/lib/amd64 -L/usr/sfw/lib/64 -L/usr/lib -L/usr/local/lib -R/usr/sfw/lib/amd64:/usr/sfw/lib/64:/usr/local/lib:/usr/lib -lsasl
LD_LIBRARY_PATH=/usr/lib/64:/lib/64:/usr/sfw/lib:/usr/local/lib:/usr/lib
CFLAGS=-m64 -I/usr/include -I/usr/local/include
CC=gcc
PATH=/usr/ccs/bin:/usr/sfw/bin:/usr/local/bin:/sbin:/usr/sbin:/usr/bin:/etc:/usr/openwin/bin:/usr/dt/bin:/usr/ucb:/usr/lib/nis:.:/usr/sbin/install.d:/usr/local/bin:/usr/ccs/bin:/usr/sfw/bin:/opt/sfw/bin
LD_LIBRARY_PATH=/usr/lib/64:/lib/64:/usr/sfw/lib:/usr/local/lib:/usr/lib

Configure is following:
./configure --prefix=/usr/local/samba --with-ads --with-ldap --with-winbind --with-krb5=/usr/local

all depends are compiled in 64 bit mode:
libiconv-1.11
openldap-2.4.17
krb5-1.3.3
db-4.7.25

Configure result:
when checking for ldap_initialize
config.log : 
Undefined                       first referenced
 symbol                             in file
ldap_initialize                     /var/tmp//ccs4Ke3Q.o

I tried on following 64 bits systems :
Solaris 8 Sparc
Solaris 10 x86
Solaris 10 Sparc
and same result !!
	
It seems that the sources can not be configured in 64 bit mode when you use openldap !
I have no problem on 32 bit mode with same configure options.

Regards,
Eric
Comment 1 Björn Jacke 2009-11-07 15:16:42 UTC
In 3.2. things like this won't be fixed any more. Can you test with 3.4 and see if that works? I guess this is fixes meanwhile. If it still doesn't work feel free to reopen this bug.