Re: Unable to compile postgresql-18.1 - Mailing list pgsql-admin

From Ibrahim Shaame
Subject Re: Unable to compile postgresql-18.1
Date
Msg-id CAJOWwD460FCkyXjMbkE6mec46EVifeWFBU=PRnFg8Xkrw1aThQ@mail.gmail.com
Whole thread Raw
In response to Re: Unable to compile postgresql-18.1  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Hello there.
Yes it was a problem with my environment. I don't know exactly what caused the problem. But after reinstall of the system the compilation went well and the problem is solved.
Thank you everyone for your help
Ibrahim Shaame 

On Wed, 21 Jan 2026, 18:56 Tom Lane, <tgl@sss.pgh.pa.us> wrote:
Ibrahim Shaame <ishaame@gmail.com> 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

pgsql-admin by date:

Previous
From: Kristjan Mustkivi
Date:
Subject: Re: autoanalyze did not run
Next
From: Laurenz Albe
Date:
Subject: Re: autoanalyze did not run