Kevin Brannen <kbran...@efji.com> writes:
> The issue is that I've not been able to make Pg use our Perl (in
> /opt/perl) instead of the system one (in /usr).
plperl.so will typically have a more or less hard-coded path to
libperl.so, eg
$ ldd ...installdir.../lib/plperl.so
linux-vdso.so.1 => (0x00007ffc613cf000)
libperl.so => /usr/lib64/perl5/CORE/libperl.so (0x00007fa315d48000)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa315b11000)
libc.so.6 => /lib64/libc.so.6 (0x00007fa31577d000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fa315563000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007fa315349000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fa315145000)
libm.so.6 => /lib64/libm.so.6 (0x00007fa314ec1000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007fa314c89000)
libutil.so.1 => /lib64/libutil.so.1 (0x00007fa314a86000)
/lib64/ld-linux-x86-64.so.2 (0x000055646d09b000)
libfreebl3.so => /lib64/libfreebl3.so (0x00007fa314883000)
You might be able to override that with LD_LIBRARY_PATH, but it's
a pain, and it will certainly not work if your homebrew libperl
isn't 100% ABI-compatible with the system one.
Personally I'd build plperl against the Perl you want to use it with.
The rest of PG isn't dependent on Perl, so you could use the community
install for the rest of it if you like.
regards, tom lane
