Re: Unable to compile postgresql-18.1

From: Ibrahim Shaame <ishaame(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-22 02:59:28
Message-ID: CAJOWwD7dHhAnF=7PXLR=525vkYaY9nnf+F79WT_Xt0FzRfAXfw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Thank you Tom
I will try to change my environment ( reinstall GCC and will let you know.
Thanks again
Ibrahim

On Wed, 21 Jan 2026, 18:56 Tom Lane, <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 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

Browse pgsql-admin by date

  From Date Subject
Next Message alexander al (leiden) 2026-01-24 12:17:55 Re: Building and installing pg_proctab
Previous Message Ibrahim Shaame 2026-01-22 02:54:39 Re: Unable to compile postgresql-18.1