Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Watkins <awatkins1966(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message
Date: 2025-07-23 19:47:06
Message-ID: 1358971.1753300026@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> I still see a way to avoid a configure check though: let's make
> src/include/port/solaris.h "#define _PAM_LEGACY_NONCONST".
> That should make OpenIndiana enough like other Solaris-alikes
> for the purpose, and we can also use that same symbol to cue
> our code how to declare the callback function.

Done that way at

https://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=635a856279ef55074dfc7a2a96c7fd686b5ff015

If you can confirm that you get a clean build with this patch,
I'd appreciate it.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2025-07-24 09:49:47 BUG #18996: Assertion fails in waiteventset.c when dropping database in single mode in PG18
Previous Message Tom Lane 2025-07-23 18:41:02 Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message