ID: 8862
User Update by: [EMAIL PROTECTED]
Old-Status: Closed
Status: Open
Bug Type: *Install and Config
Description: libtool does not code runpath into

Of course I know about LD_LIBRARY_PATH. This is at best a bad
workaround. A well-build program should not require LD_LIBRARY_PATH
but have the correct runpath coded into it.

Previous Comments:

[2001-01-24 20:43:56] [EMAIL PROTECTED]
You must use LD_LIBRARY_PATH environment variable.
ie. Do:
# export LD_LIBRARY_PATH=/export/www/apache/lib:/export/www/mysql/lib/mysql
before starting apache.



[2001-01-23 11:06:33] [EMAIL PROTECTED]
The configure arguments also contained


[2001-01-23 10:59:20] [EMAIL PROTECTED]
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 references shared (in
/export/www/apache/lib) and (in
/export/www/mysql/lib/mysql) and thus should have the runpath
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.)


Full Bug description available at:

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to