| From: | Robins Tharakan <tharakan(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Sam James <sam(at)gentoo(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Build failure with GCC 15 (defaults to -std=gnu23) |
| Date: | 2024-12-07 11:42:07 |
| Message-ID: | CAEP4nAyRfWZ8T8xzNHHy4p8kLCrXAAY7Hbs2_P8YCOJiu=6SCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, 30 Nov 2024 at 02:02, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robins Tharakan <tharakan(at)gmail(dot)com> writes:
> > alligator/HEAD is still failing though.
> > Let me know if changing something on alligator can help in some way.
>
> I think we're waiting on the gcc crew to fix their bug. As long
> as alligator is faithfully rebuilding gcc from upstream everyday,
> there's not much more to do than wait.
>
> (You could adopt Andres' -g1 workaround, but then we'd not know
> when the gcc bug is fixed. So unless this drags on quite awhile,
> I think alligator is best left as-is.)
>
It's been a few days since alligator lit up the buildfarm red. IMHO at this
point, it is just noise. So I've reduced its v16+ build frequency to daily
(instead of a few minutes). I'll revert that once gcc is fixed upstream.
-
robins
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-12-07 17:49:45 | Re: FF3 vs MS Date/Time Template - ERROR: date/time field value out of range |
| Previous Message | Tom Lane | 2024-12-07 00:07:41 | Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows |