I'm trying to figure out what the libtool is doing in php. After running 'make install' it shows that the modules were properly copied over to apache's libexec folder like I would expect. The part I don't fully understand is it tells me to run `libtool --finish /home/solaris5/php-5.2.3/libs'. What exactly is it that that command does? When running that command it it tells you the following:
#libtool --finish /home/solaris5/php-5.2.3/libs
----------------------------------------------------------------------
Libraries have been installed in:
/home/solaris5/php-5.2.3/libs
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- use the `-RLIBDIR' linker flag
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
The funny thing about this is that those libraries were allready in that folder. Additionally I typically blow away source code folders after installs so why would I want to keep these in there. I check /usr/local/lib yet nothing was added there. I checked /usr/lib and thank God nothing was added there. Can anyone provide me with a little further insight on what is actually happening? PHP runs fine as an apache module even if I don't run this command.
The pertinent info after running 'make install' is:
Installing PHP SAPI module: apache2handler
/var/apache2/build/instdso.sh SH_LIBTOOL='/var/apache2/build/libtool' libphp5.la /usr/apache2/libexec
/var/apache2/build/libtool --mode=install cp libphp5.la /usr/apache2/libexec/
cp .libs/libphp5.so /usr/apache2/libexec/libphp5.so
chmod +x /usr/apache2/libexec/libphp5.so
cp .libs/libphp5.lai /usr/apache2/libexec/libphp5.la
libtool: install: warning: remember to run `libtool --finish /home/solaris5/php-5.2.3/libs'
chmod 755 /usr/apache2/libexec/libphp5.so
Thanks for reading this long post,
Craig
#libtool --finish /home/solaris5/php-5.2.3/libs
----------------------------------------------------------------------
Libraries have been installed in:
/home/solaris5/php-5.2.3/libs
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- use the `-RLIBDIR' linker flag
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
The funny thing about this is that those libraries were allready in that folder. Additionally I typically blow away source code folders after installs so why would I want to keep these in there. I check /usr/local/lib yet nothing was added there. I checked /usr/lib and thank God nothing was added there. Can anyone provide me with a little further insight on what is actually happening? PHP runs fine as an apache module even if I don't run this command.
The pertinent info after running 'make install' is:
Installing PHP SAPI module: apache2handler
/var/apache2/build/instdso.sh SH_LIBTOOL='/var/apache2/build/libtool' libphp5.la /usr/apache2/libexec
/var/apache2/build/libtool --mode=install cp libphp5.la /usr/apache2/libexec/
cp .libs/libphp5.so /usr/apache2/libexec/libphp5.so
chmod +x /usr/apache2/libexec/libphp5.so
cp .libs/libphp5.lai /usr/apache2/libexec/libphp5.la
libtool: install: warning: remember to run `libtool --finish /home/solaris5/php-5.2.3/libs'
chmod 755 /usr/apache2/libexec/libphp5.so
Thanks for reading this long post,
Craig