Re: Unable to compile postgresql-18.1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ibrahim Shaame <ishaame(at)gmail(dot)com>
Cc: Erik Wienhold <ewie(at)ewie(dot)name>, pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Unable to compile postgresql-18.1
Date: 2026-01-21 15:56:03
Message-ID: 2206547.1769010963@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Ibrahim Shaame <ishaame(at)gmail(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Thomas Carroll 2026-01-21 16:06:58 Re: Sybase to postgres Timestamp column
Previous Message Tom Lane 2026-01-21 15:06:35 Re: Sybase to postgres Timestamp column