Re: ABI Compliance Checker GSoC Project - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ABI Compliance Checker GSoC Project
Date
Msg-id 2065294.1769808164@sss.pgh.pa.us
Whole thread Raw
In response to Re: ABI Compliance Checker GSoC Project  (Dean Rasheed <dean.a.rasheed@gmail.com>)
Responses Re: ABI Compliance Checker GSoC Project
List pgsql-hackers
Dean Rasheed <dean.a.rasheed@gmail.com> writes:
> On Thu, 29 Jan 2026 at 14:18, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I think this means that Andrew just forgot that step, and it will
>> go away by itself when you push the .abi-compliance-history
>> changes (forcing a rebuild of the cached abidw output).

> Ah, I see. Thanks for the explanation. I have pushed the
> .abi-compliance-history patch and the checks on crake are starting to
> turn green.

crake is now green except on the v14 branch.  That's because Dean
did not push any .abi-compliance-history addition there, so it's
still working with an abidw reference-commit result that doesn't
account for --headersdir.  That's going to need manual cache-flushing
I think; I'm not aware of any other impending ABI changes for v14.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 001_password.pl fails with --without-readline
Next
From: Nathan Bossart
Date:
Subject: Re: refactor architecture-specific popcount code