Re: [PATCH] Fix build on MINGW on ARM64

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: vignesh C <vignesh21@gmail.com>, Lars Kanis <lars@greiz-reinsdorf.de>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-04-07T15:05:27Z
Lists: pgsql-hackers
On 2025-04-07 Mo 12:58 AM, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> On 2025-04-01 Tu 11:15 AM, Andrew Dunstan wrote:
>>> On 2025-04-01 Tu 8:47 AM, vignesh C wrote:
>>>> There is an existing CF entry for this at [1]. If no one picks this
>>>> till the end of this CF, we can move it to next CF.
>>>> [1] - https://commitfest.postgresql.org/patch/5610/
>>> Somehow I missed that. OK, looks good, will commit shortly.
>> Done
> fairywren has been failing rather horribly since this went in [1].
> It's not certain of course that this commit broke it and not one
> of the other ones that first appeared in that build -- but none
> of the other ones look plausibly related.
>
> 			regards, tom lane
>
> [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2025-04-02%2007%3A06%3A04



Yes, that was indeed the problem. I have reverted the patch.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




Commits

  1. Revert "Use workaround of __builtin_setjmp only on MINGW on MSVCRT"

  2. Use workaround of __builtin_setjmp only on MINGW on MSVCRT