Re: PostgreSQL C++ Interface version 14.9 using static library instead of shared library - Mailing list pgsql-general

From Tom Lane
Subject Re: PostgreSQL C++ Interface version 14.9 using static library instead of shared library
Date
Msg-id 3768987.1697812843@sss.pgh.pa.us
Whole thread Raw
In response to PostgreSQL C++ Interface version 14.9 using static library instead of shared library  (M Tarkeshwar Rao <m.tarkeshwar.rao@ericsson.com>)
List pgsql-general
M Tarkeshwar Rao <m.tarkeshwar.rao@ericsson.com> writes:
> While compiling PostgreSQL C++ Interface version 14.9 . Found that libpq.so is getting created with libssl.a and
libcrypto.ainstead of shared library libssl.so and libcrypto.so. 

I don't see that happening here ...

$ ldd libpq.so.5.14
        linux-vdso.so.1 (0x00007ffea6b41000)
        libssl.so.1.1 => /lib64/libssl.so.1.1 (0x00007fc3be4b1000)
        libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007fc3bdfc7000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fc3bdda7000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fc3bd9e2000)
        libz.so.1 => /lib64/libz.so.1 (0x00007fc3bd7ca000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fc3bd5c6000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fc3be991000)

$ size libpq.so.5.14
   text    data     bss     dec     hex filename
 295038   12388     480  307906   4b2c2 libpq.so.5.14

It seems likely that there's some oddity in your build environment.
Maybe the libssl.so and libcrypto.so symlinks aren't present?  Or take
a close look at the command that links libpq.so, and see if any odd
switches have crept in.

            regards, tom lane



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Is postgres_fdw "safe"?
Next
From: Ron
Date:
Subject: Re: Is postgres_fdw "safe"?