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 1s35O0-009DPd-Uf for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 02:44:28 +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 1s35Ny-00E9ui-Bf for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 02:44:27 +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 1s35Ny-00E9ua-0n for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 02:44:26 +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 1s35Nw-001KqH-Dj for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 02:44:25 +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 4442iNwv2798895; Fri, 3 May 2024 22:44:23 -0400 From: Tom Lane To: AJ ONeal cc: "pgsql-general@lists.postgresql.org" Subject: Re: How to Build Postgres in a Portable / Relocatable fashion? In-reply-to: References: <2770930.1714779894@sss.pgh.pa.us> Comments: In-reply-to AJ ONeal message dated "Sat, 04 May 2024 00:12:55 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2798893.1714790663.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 03 May 2024 22:44:23 -0400 Message-ID: <2798894.1714790663@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk AJ ONeal writes: > It seems like the first bit of magic I need is: > `--prefix=3D/doesntexist/postgres` No, you want an actual path so that "make install" will succeed. The point is that then you can tar up that installation tree (relative to its top) and untar it somewhere else. > I'd like to build as much static as possible (or reasonable). Is there a= way to tell it "just include openssl"? No, and are you really sure you want that? Then it's on you to rebuild and redistribute, pronto, every time openssl issues a security fix. There's a reason why most Linux distros forbid static linking of libraries from different sources. regards, tom lane