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.96) (envelope-from ) id 1wA7JX-0024sN-2A for pgsql-general@arkaria.postgresql.org; Tue, 07 Apr 2026 14:21:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wA7JV-000bAs-3A for pgsql-general@arkaria.postgresql.org; Tue, 07 Apr 2026 14:21:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wA7JV-000bAk-27 for pgsql-general@lists.postgresql.org; Tue, 07 Apr 2026 14:21:58 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wA7JT-000000017cN-0bYJ for pgsql-general@lists.postgresql.org; Tue, 07 Apr 2026 14:21:57 +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 637ELm4w2040886; Tue, 7 Apr 2026 10:21:48 -0400 From: Tom Lane To: Matthias Apitz cc: pgsql-general@lists.postgresql.org Subject: Re: configure && --with In-reply-to: References: Comments: In-reply-to Matthias Apitz message dated "Tue, 07 Apr 2026 11:15:08 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2040884.1775571708.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 07 Apr 2026 10:21:48 -0400 Message-ID: <2040885.1775571708@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Matthias Apitz writes: > Why the setting of '--with-ssl=3D/usr/local/sisis-pap/lib' as adviced by > the help of ./configure: > $ ./configure --help | grep 'with-ssl=3DLIB' > --with-ssl=3DLIB use LIB for SSL/TLS support (openssl) > is not used for the run check of the openssl binary as LD_LIBRARY_PATH? If you had checked the manual, you would have read --with-ssl=3DLIBRARY = Build with support for SSL (encrypted) connections. The only LIBRARY supported is openssl, which is used for both OpenSSL and LibreSSL. So the argument is just pro-forma at the moment, although someday maybe it will do something. The options you need to use to point it at a non-default openssl installation are --with-includes and --with-libraries [1]. regards, tom lane [1] https://www.postgresql.org/docs/current/install-make.html#CONFIGURE-OP= TIONS-BUILD-PROCESS