PHP 4.0 Bug #8862: libtool does not code runpath into libphp4.so

From: Date: Tue, 23 Jan 2001 15:59:20 +0000
Subject: PHP 4.0 Bug #8862: libtool does not code runpath into libphp4.so
Groups: php.dev 
Request: Send a blank email to php-dev+get-44823@lists.php.net to get a copy of this message
From: strube@physik3.gwdg.de Operating system: Solaris 7 (SPARC) PHP version: 4.0.4pl1 PHP Bug Type: *Install and Config Bug description: libtool does not code runpath into libphp4.so Apache php module configured with: env CC=/opt/SUNWspro/bin/cc CFLAGS=-xO2 ./configure --with-apxs=/export/www/apache/sbin/apxs --with-ndbm --with-db --with-mysql=/export/www/mysql --enable-yp --enable-sysvsem --enable-sysvshm --with-exec-dir=/export/www/php/bin --enable-versioning --with-config-file-path=/export/www/php/lib --prefix=/export/www/php --disable-debug The resulting libphp4.so references shared libdb2.so (in /export/www/apache/lib) and libmysqlclient.so (in /export/www/mysql/lib/mysql) and thus should have the runpath -R/export/www/apache/lib:/export/www/mysql/lib/mysql coded into it. This does not happen, although the make log shows the presence of the -R options when libtool is called. Dirty workaround: After configure, change line 1082 in libtool: < linkopts= --- > linkopts=-R/export/www/apache/lib:/export/www/mysql/lib/mysql (Apache itself does not have this runpath. Of course, this would suggest another workaround, but one should not rely on this for an independently added module.) -- Edit Bug report at: http://bugs.php.net/?id=8862&edit=1

« previous php.dev (#44823) next »