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 1rD5nu-000sLD-Qf for pgsql-general@arkaria.postgresql.org; Tue, 12 Dec 2023 16:40:18 +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 1rD5nt-006eO6-Hj for pgsql-general@arkaria.postgresql.org; Tue, 12 Dec 2023 16:40:17 +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 1rD5nt-006eNw-5Y for pgsql-general@lists.postgresql.org; Tue, 12 Dec 2023 16:40:17 +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 1rD5nq-00Bcts-Fc for pgsql-general@lists.postgresql.org; Tue, 12 Dec 2023 16:40:16 +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 3BCGeCVV2447029; Tue, 12 Dec 2023 11:40:12 -0500 From: Tom Lane To: Ayush Vatsa cc: Ian Lawrence Barwick , pgsql-general@lists.postgresql.org Subject: Re: Assistance Needed: Error during PostgreSQL Configuration In-reply-to: References: <2169650.1702306225@sss.pgh.pa.us> Comments: In-reply-to Ayush Vatsa message dated "Mon, 11 Dec 2023 22:47:53 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2447027.1702399212.1@sss.pgh.pa.us> Date: Tue, 12 Dec 2023 11:40:12 -0500 Message-ID: <2447028.1702399212@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Ayush Vatsa writes: > Sorry, I should have included the required information initially itself. I > am new to the database field so please pardon my mistakes :) You still didn't mention the platform/environment, but I guess from the reference to -isysroot that it must be macOS (Darwin). I further guess that you're using Homebrew or MacPorts, because bare macOS doesn't supply GNU sed. That doesn't get us much further though; plenty of Postgres developers use one or the other of those setups without difficulty. One idea that comes to mind is that you might be trying to build in a directory path that contains spaces or other odd characters. That's generally not well supported by Unix-based tooling. However, I'm not sure how that'd lead to this particular failure. The only other idea I have is that maybe you have some weird Homebrew or MacPorts package installed that changes the behavior of your shell. I have no idea what that would be though. FWIW, on my own Mac laptop, line 486 in config.status in a current build looks like *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;; which seems identical to what you reported. So that takes some steam out of the idea that the file was generated incorrectly in your build, pointing more to the idea that your shell is not reading it as-expected. regards, tom lane