OpenLDAP Faq-O-Matic: AIX Linking Problems

	OpenLDAP Faq-O-Matic : OpenLDAP Software FAQ : Installation : Platform Hints : IBM AIX : AIX Linking Problems
	It appears many of the AIX linking problems are directly attributable to the broken (hardcoded) libpath passed to the linker form build/ltconfig. For example: hardcode_default_flag='${wl}-b nolibpath' I tried setting the libpath to AIX's ld via: LDFLAGS="-Wl,-blibpath:/usr/local/lib:/usr/opt/freeware:/usr/lib:/lib" It does not honor this override, as it sticks the nolibpath on the end like so: .... -lssl -lcrypto -lsasl -b nolibpath I know the guys who create the linux toolbox packages have a patch (I don't know who authored it) that fixes this and other problems with ltconfig among other things. Hopefully this will same everyone else some problems with the linking errors. This is pretty easy to handle by hand, but requires a patch for someone building an RPM. jes@e-techservices.com
	I ultimately was able to address this by setting LIBPATH in my shell, before I ran an rpm -ba openldap.spec. When the broken ltconfig appends noblibpath to the end of the LIBS variable, it forces the blibpath to the default of /usr/lib:/lib. If LIBPATH is set, it will use LIBPATH instead. If you are having trouble building openldap on AIX with SASL and TLS/SSL support this is a likely reason. jes@e-techservices.com
	You can use the command "dump -H <binary>" to allow you to see the library path compiled into your binary. jes@e-techservices.com
	[Append to This Answer]

Previous:	Running "make depend" causes problems?
Next:	Problems with "make test"

	[Search]	[Appearance]
This is a Faq-O-Matic 2.721.test.