Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l07Cs-0003SV-FA for pgsql-bugs@arkaria.postgresql.org; Thu, 14 Jan 2021 18:18:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l07Cr-0007Zn-5p for pgsql-bugs@arkaria.postgresql.org; Thu, 14 Jan 2021 18:18:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l07Cq-0007Zg-Vp for pgsql-bugs@lists.postgresql.org; Thu, 14 Jan 2021 18:18:48 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l07Co-0007TS-Lu for pgsql-bugs@postgresql.org; Thu, 14 Jan 2021 18:18:47 +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 10EIIhEx1418719; Thu, 14 Jan 2021 13:18:43 -0500 From: Tom Lane To: Tim Kelly cc: pgsql-bugs@postgresql.org Subject: Re: questions about porting postgresql to older operating system In-reply-to: <600073D8.8010604@dialectronics.com> References: <600073D8.8010604@dialectronics.com> Comments: In-reply-to Tim Kelly message dated "Thu, 14 Jan 2021 11:39:52 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1418717.1610648323.1@sss.pgh.pa.us> Date: Thu, 14 Jan 2021 13:18:43 -0500 Message-ID: <1418718.1610648323@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Tim Kelly writes: > 1) Starting with gmake, what specific functionality is required that can > not be duplicated with manually crafting Makefiles? We've never worried about building with non-GNU make. If you really want to translate all of the Makefiles to old-style make syntax, it might be possible, but it sure seems like a lot of make-work (pun intended). > 2a) Can postgresql run without pthread support? Definitely; we still have at least one buildfarm animal without that. > 3) Can postgresql still work without dynamic loading support? mmm ... in principle yes, but you'll lose one heck of a lot of functionality that's implemented in extension modules. Possibly that could be worked around by deciding which extensions you need and statically binding them into the backend executable. Again, that's not a case we've worried about for the last twenty years or so, so there's likely to be some pain there. regards, tom lane