Phil Howard <phil-pgsql-general@ipal.net> writes:
> I compiled 7.3.2 and built a binary tarball to distribute to other
> machines. But the building, in particular the linking, has a problem
> in the way it links to libssl. Instead of making the linking reference
> to the generic version level of the library, it makes it to the specific
> patch level version. The end result is that the compiled binary won't
> run unless that EXACT version of libssl is present.
Hmm. When I build from source on a Linux box, I get generic references.
For example, in a recent build on a RHL 8.0 box, I see:
[tgl@rh1 bin]$ ldd psql
libpq.so.3 => /home/tgl/testversion/lib/libpq.so.3 (0x40013000)
libssl.so.2 => /lib/libssl.so.2 (0x4003e000)
libcrypto.so.2 => /lib/libcrypto.so.2 (0x4006e000)
libz.so.1 => /usr/lib/libz.so.1 (0x40142000)
libreadline.so.4 => /usr/lib/libreadline.so.4 (0x40150000)
libtermcap.so.2 => /lib/libtermcap.so.2 (0x4017c000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x40180000)
libresolv.so.2 => /lib/libresolv.so.2 (0x401ae000)
libnsl.so.1 => /lib/libnsl.so.1 (0x401c0000)
libdl.so.2 => /lib/libdl.so.2 (0x401d5000)
libm.so.6 => /lib/i686/libm.so.6 (0x401d8000)
libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
[tgl@rh1 bin]$ ldd postgres
libssl.so.2 => /lib/libssl.so.2 (0x4002c000)
libcrypto.so.2 => /lib/libcrypto.so.2 (0x4005d000)
libz.so.1 => /usr/lib/libz.so.1 (0x40131000)
libreadline.so.4 => /usr/lib/libreadline.so.4 (0x4013f000)
libtermcap.so.2 => /lib/libtermcap.so.2 (0x4016b000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x4016f000)
libresolv.so.2 => /lib/libresolv.so.2 (0x4019c000)
libnsl.so.1 => /lib/libnsl.so.1 (0x401af000)
libdl.so.2 => /lib/libdl.so.2 (0x401c4000)
libm.so.6 => /lib/i686/libm.so.6 (0x401c7000)
libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
[tgl@rh1 bin]$
This seems correct to me. What does ldd show for you?
regards, tom lane
