| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Mankirat Singh <mankiratsingh1315(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Subject: | Re: ABI Compliance Checker GSoC Project |
| Date: | 2026-01-30 21:22:44 |
| Message-ID: | 2065294.1769808164@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
> On Thu, 29 Jan 2026 at 14:18, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2026-01-30 21:33:19 | Re: refactor architecture-specific popcount code |
| Previous Message | Tom Lane | 2026-01-30 20:13:47 | Re: 001_password.pl fails with --without-readline |