Hi all,
I've been attempting to build PHP on Redhat 3 for weeks, and have been unable to discover the problem. I was wondering if anyone here could help. I am trying to build php 4.3.11, using the following configure options:
./configure --prefix=/users/home/mttt/php4.3 --with-ldap=/users/home/mttt/openldap --enable-so --libdir=/usr/lib
I get the following error when executing 'make':
ext/standard/dl.o(.text+0x143): In function `php_dl':
/users/home/mttt/php-4.3.11/ext/standard/dl.c:141: Using 'dlopen' in
statically
linked applications requires at runtime the shared libraries from the
glibc vers
ion used for linking
ext/mysql/libmysql/my_tempnam.o(.text+0x40): In function `my_tempnam':
/users/home/mttt/php-4.3.11/ext/mysql/libmysql/my_tempnam.c:115: the use
of `tem
pnam' is dangerous, better use `mkstemp'
/usr/lib/gcc-lib/i386-redhat-linux/3.2.3/../../../libdl.a(dlsym.o)(.text+0x23):
In function `dlsym':
: undefined reference to `_dl_load_lock'
/usr/lib/gcc-lib/i386-redhat-linux/3.2.3/../../../libdl.a(dlsym.o)(.text+0x4d):
In function `dlsym':
: undefined reference to `_dl_load_lock'
collect2: ld returned 1 exit status
make: *** [sapi/cgi/php] Error 1
System: RHEL 3, Intel x86.
Thanks for your help.
Building PHP with LDAP support on RHEL3
Moderator: General Moderators
Re: Building PHP with LDAP support on RHEL3
Any ideas about this? Still encountering the same error, even without LDAP support. 
Re: Building PHP with LDAP support on RHEL3
Make sure your glibc library is up-to-date would be my guess.The errors wrote:Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
Real programmers don't comment their code. If it was hard to write, it should be hard to understand.
Re: Building PHP with LDAP support on RHEL3
The one on the system is libc.so.6, version 2.3.2-95.37. Shouldn't this be adequate?
Last edited by r590 on Mon Mar 03, 2008 12:50 pm, edited 1 time in total.
Re: Building PHP with LDAP support on RHEL3
Sorry - no clue. I was just interpreting the error messages. I've never come across this particular error when compiling PHP. In my experience though, doing a Google search for the exact error message (or perhaps without explicitely stating the software versions), usually gets you someone who's had the problem before.
Real programmers don't comment their code. If it was hard to write, it should be hard to understand.