summaryrefslogtreecommitdiff
path: root/HISTORY
diff options
context:
space:
mode:
authorTom Lane2025-07-23 19:44:29 +0000
committerTom Lane2025-07-23 19:44:29 +0000
commit3d039b53a1339791f89b68580ba462f2bb4dfa52 (patch)
tree94379bc675f1aeb5f3fdd0def8103fc1d539f347 /HISTORY
parent7b98c5536818287998ca868dc96a8dc20ea78f0b (diff)
Fix build breakage on Solaris-alikes with late-model GCC.REL_18_STABLE
Solaris has never bothered to add "const" to the second argument of PAM conversation procs, as all other Unixen did decades ago. This resulted in an "incompatible pointer" compiler warning when building --with-pam, but had no more serious effect than that, so we never did anything about it. However, as of GCC 14 the case is an error not warning by default. To complicate matters, recent OpenIndiana (and maybe illumos in general?) *does* supply the "const" by default, so we can't just assume that platforms using our solaris template need help. What we can do, short of building a configure-time probe, is to make solaris.h #define _PAM_LEGACY_NONCONST, which causes OpenIndiana's pam_appl.h to revert to the traditional definition, and hopefully will have no effect anywhere else. Then we can use that same symbol to control whether we include "const" in the declaration of pam_passwd_conv_proc(). Bug: #18995 Reported-by: Andrew Watkins <awatkins1966@gmail.com> Author: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/18995-82058da9ab4337a7@postgresql.org Backpatch-through: 13
Diffstat (limited to 'HISTORY')
0 files changed, 0 insertions, 0 deletions