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 1swo4R-0068he-Lf for pgsql-general@arkaria.postgresql.org; Fri, 04 Oct 2024 19:34:36 +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 1swo4P-004qUv-V6 for pgsql-general@arkaria.postgresql.org; Fri, 04 Oct 2024 19:34:33 +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.94.2) (envelope-from ) id 1swo4P-004qUm-JQ for pgsql-general@lists.postgresql.org; Fri, 04 Oct 2024 19:34:33 +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.94.2) (envelope-from ) id 1swo4K-002YXv-Os for pgsql-general@postgresql.org; Fri, 04 Oct 2024 19:34:33 +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 494JYJPS680040; Fri, 4 Oct 2024 15:34:19 -0400 From: Tom Lane To: Christophe Pettus cc: Corbin Cavolt , "pgsql-general@postgresql.org" Subject: Re: Error Building Postgres 17.0 from Source In-reply-to: <4A3CC287-BAC9-4786-B4F9-FFF5B2CA78F9@thebuild.com> References: <676935.1728068724@sss.pgh.pa.us> <4A3CC287-BAC9-4786-B4F9-FFF5B2CA78F9@thebuild.com> Comments: In-reply-to Christophe Pettus message dated "Fri, 04 Oct 2024 12:08:11 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <680038.1728070459.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 04 Oct 2024 15:34:19 -0400 Message-ID: <680039.1728070459@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Christophe Pettus writes: > On Oct 4, 2024, at 12:05, Tom Lane wrote: >> Yeah, that's what it looks like. I'm a bit confused though because >> 16.x should have failed the same way: building our docs without local >> DTDs has failed for well over a year now [1]. = > To add confusion to the fire, I was successfully building pre-17 version= s ("make world") locally on MacOS fine without having to install the docum= entation tools. It wasn't until 17 that it failed (and installing the doc= tools as recommended fixed it). If you had a locally installed copy of the required DTDs, it should've worked, but otherwise I don't see how ... oh, wait. Were you building from a source tarball? If so, the difference is that up to v16 we included prebuilt HTML docs in the tarballs, but as of v17 we don't. So "make world" now triggers a local docs build where before it didn't. You can restore things to the status quo ante if you also download the now-separate docs tarball, eg https://ftp.postgresql.org/pub/source/v17.0/postgresql-17.0-docs.tar.gz and unpack that into the same place as the main source tarball. regards, tom lane