On Wed, 17 Jun 2026 at 13:46, Robins Tharakan <tharakan@gmail.com> wrote:
> Earlier, since gcc HEAD was too noisy, I moved them all to gcc v15
> assuming it'd be better. The gcc build script has been stable and there's
> been no change in any of the machines recently, so I also wouldn't be
> surprised if it is gcc again.
>
> For now, I've taken them all offline and unless someone has a better
> idea, I'll switch them to stay pinned to the recentmost gcc release
> version - rationale being that if a tagged gcc release is buggy, it
> may be interesting to know about.
FWIW the error that alvaro mentions suggests that either the C++
stdlib was not installed (i.e. some installation/configuration
problem) or that extern "C++" {...} is broken.
