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 1rSoeu-00G6Ty-8K for pgsql-general@arkaria.postgresql.org; Thu, 25 Jan 2024 01:36:00 +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 1rSoet-00AcGS-FC for pgsql-general@arkaria.postgresql.org; Thu, 25 Jan 2024 01:35:59 +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 1rSoet-00AcGJ-0B for pgsql-general@lists.postgresql.org; Thu, 25 Jan 2024 01:35:59 +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 1rSoeq-003Djn-Mk for pgsql-general@lists.postgresql.org; Thu, 25 Jan 2024 01:35: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 40P1Zti5246865; Wed, 24 Jan 2024 20:35:55 -0500 From: Tom Lane To: Michael Nolan cc: Daniel Gustafsson , "pgsql-generallists.postgresql.org" Subject: Re: undefined symbol when installing pgcrypto on 16.1 In-reply-to: References: <334461.1705013937@sss.pgh.pa.us> <2271455.1705593108@sss.pgh.pa.us> <240616.1706143511@sss.pgh.pa.us> Comments: In-reply-to Michael Nolan message dated "Wed, 24 Jan 2024 19:32:07 -0600" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <246863.1706146555.1@sss.pgh.pa.us> Date: Wed, 24 Jan 2024 20:35:55 -0500 Message-ID: <246864.1706146555@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Nolan writes: > Including --with-openssl does include the crypto library, but if I > don't do a 'make clean' before doing a make, I get errors when > compiling postgresql. Apparently is it always a good idea to do make > clean when reconfiguring postgresql. Indeed. In theory, if you use --enable-depend, you needn't do "make clean". But I don't trust that a whole lot personally. I find that using ccache gets most of the win with fewer assumptions. regards, tom lane