On Tuesday 17 September 2002 02:58 pm, Cindy wrote:
> Lamar Owen writes:
> >On Tuesday 17 September 2002 02:42 pm, Cindy wrote:
> >> OK, related question while I wait for my admin to respond. Assuming
> >> the shared libary package is available in some other directory, I'm
> >> assuming I'm still going to have to do something to wind up with a
> >> libperl.so in the /usr/local/pgsql/lib directory.
> >Perl itself has to be rebuilt to provide libperl.so
> Not if the shared library is in fact already built? It very well
> may be on this system, I'm working at a university which has an
> overall administration in place on top of the individual unix boxes,
> and practically nothing is in standard paths (infuriating, but...).
> So if it's already there, just in some oddball directory, I shd
> be able to use it?
> Oh, and if libperl.so is from a perl compilation why is it in psql's lib
> dir? Does it get copied there at some point in installation?
The file libperl.so is a dynamically linkable version of the embeddable
libperl.a. This allows an extension module to embed perl in itself. The
plperl.so module is a 'wrapper' with a few extra features that embeds the
whole perl interpreter (libperl.so) into the backend.
It shouldn't be in the psql libdir; it should be in a system libdir. If you
have sufficient privileges to do so, do a 'find / -name "libperl.so*" -print'
and see if it is anywhere on your system in a place the dynamic loader
(ld.so) can find it.
To recap:
1.) plperl.so is the PL/Perl extension module provided as part of the
PostgreSQL distribution;
2.) libperl.so is the perl interpreter suitable for dynamic loading into an
extension module and is provided by the perl package;
3.) 1 uses 2.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11