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.96) (envelope-from ) id 1viaZ3-00AVu7-1f for pgsql-admin@arkaria.postgresql.org; Wed, 21 Jan 2026 15:56:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1viaZ1-007yjE-0E for pgsql-admin@arkaria.postgresql.org; Wed, 21 Jan 2026 15:56:11 +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.96) (envelope-from ) id 1viaZ0-007yj6-2H for pgsql-admin@lists.postgresql.org; Wed, 21 Jan 2026 15:56:11 +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.96) (envelope-from ) id 1viaYy-001k4j-1y for pgsql-admin@lists.postgresql.org; Wed, 21 Jan 2026 15:56:10 +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 60LFu3682206548; Wed, 21 Jan 2026 10:56:03 -0500 From: Tom Lane To: Ibrahim Shaame cc: Erik Wienhold , pgsql-admin Subject: Re: Unable to compile postgresql-18.1 In-reply-to: References: <01c5d88c-e7d7-4a52-985c-d9dabc0f670a@ewie.name> Comments: In-reply-to Ibrahim Shaame message dated "Wed, 21 Jan 2026 09:49:07 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2206546.1769010963.1@sss.pgh.pa.us> Date: Wed, 21 Jan 2026 10:56:03 -0500 Message-ID: <2206547.1769010963@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Ibrahim Shaame writes: > Thank you for the response. As for LIBRARY_PATH, I have always manually > compiled postgresql and I don't explicitly mention the LIBRARY_PATH > directory. That's why I am surprised why this time with this subversion > doesn't work just as it worked in the last version. There is nothing in that area that we changed between 18.0 and 18.1; moreover, if we had broken something like that, it's highly unlikely that nobody but you would have noticed. You need to look at what changed in your build environment. gcc seems to be getting confused by the fact that src/test/isolation contains a subdirectory named "specs", but that's been there for years. The most likely explanation is that some environment variable is causing gcc to look in the current directory for its spec file (although I don't see any documentation of such a variable in the gcc manual). It's also plausible I guess that you have a corrupted gcc installation. regards, tom lane