Thomas Munro <[email protected]> writes:
> On Sat, Feb 7, 2026 at 9:31 AM Tom Lane <[email protected]> wrote:
>> Perhaps, but since we're getting pretty hard up against the release
>> freeze deadline, I think the thing to do for today is just to update
>> .abi-compliance-history. We know that way works.
> So it seems I need to do the attached for 18, and the same again for
> 17 and 16. Look about right?
Right.
> I peeked at the libabigail man page, and I don't see any discussion of
> incomplete types, but it looks like OPAQUE_TYPE_LABEL might be a way
> to tell it about this. If that works, wouldn't it be better than
> doing this forever? Where would that be configured?
It looks like that is something you write in a suppression file.
I think it might be too strong for our purposes though: looks like
it blocks *any* complaints related to that type. That'd be
problematic, especially if you can't suppress on just
"struct config_generic[]" without affecting "struct config_generic".
On the whole I think a bit of research and testing would be needed
to go that way. Not to mention a buildfarm client change to get
the abidw calls to pick up the suppression files.
regards, tom lane
