Re: Build failure with GCC 15 (defaults to -std=gnu23) - Mailing list pgsql-bugs

From Robins Tharakan
Subject Re: Build failure with GCC 15 (defaults to -std=gnu23)
Date
Msg-id CAEP4nAyRfWZ8T8xzNHHy4p8kLCrXAAY7Hbs2_P8YCOJiu=6SCA@mail.gmail.com
Whole thread Raw
In response to Re: Build failure with GCC 15 (defaults to -std=gnu23)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Build failure with GCC 15 (defaults to -std=gnu23)
List pgsql-bugs

On Sat, 30 Nov 2024 at 02:02, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Robins Tharakan <tharakan@gmail.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
Next
From: Tom Lane
Date:
Subject: Re: FF3 vs MS Date/Time Template - ERROR: date/time field value out of range