Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qtqgJ-00ED7b-Na for pgsql-general@arkaria.postgresql.org; Fri, 20 Oct 2023 14:40:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qtqgH-002uMA-95 for pgsql-general@arkaria.postgresql.org; Fri, 20 Oct 2023 14:40:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qtqgG-002uLF-TR for pgsql-general@lists.postgresql.org; Fri, 20 Oct 2023 14:40:53 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qtqgA-001RR0-TJ for pgsql-general@postgresql.org; Fri, 20 Oct 2023 14:40:52 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 39KEehJx3768988; Fri, 20 Oct 2023 10:40:43 -0400 From: Tom Lane To: M Tarkeshwar Rao cc: "pgsql-general@postgresql.org" , Nikhil Bhatia Subject: Re: PostgreSQL C++ Interface version 14.9 using static library instead of shared library In-reply-to: References: Comments: In-reply-to M Tarkeshwar Rao message dated "Fri, 20 Oct 2023 10:50:07 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3768986.1697812843.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 20 Oct 2023 10:40:43 -0400 Message-ID: <3768987.1697812843@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk M Tarkeshwar Rao writes: > While compiling PostgreSQL C++ Interface version 14.9 . Found that libpq= .so is getting created with libssl.a and libcrypto.a instead of shared lib= rary 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 =3D> /lib64/libssl.so.1.1 (0x00007fc3be4b1000) libcrypto.so.1.1 =3D> /lib64/libcrypto.so.1.1 (0x00007fc3bdfc7000) libpthread.so.0 =3D> /lib64/libpthread.so.0 (0x00007fc3bdda7000) libc.so.6 =3D> /lib64/libc.so.6 (0x00007fc3bd9e2000) libz.so.1 =3D> /lib64/libz.so.1 (0x00007fc3bd7ca000) libdl.so.2 =3D> /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