Re: [OE-core] [PATCH 2/2] rust: Upgrade 1.78.0->1.79.0

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2024-08-27 at 19:16 +0200, Alexander Kanavin wrote:
> On Tue, 27 Aug 2024 at 18:25, Alexander Kanavin via
> lists.openembedded.org
> <alex.kanavin=gmail.com@lists.openembedded.org>
> wrote:
> > 
> > On Tue, 27 Aug 2024 at 18:23, Alexander Kanavin via
> > lists.openembedded.org
> > <alex.kanavin=gmail.com@lists.openembedded.org>
> > wrote:
> > > I just reproduced this on autobuilder's alma9 in a private build
> > > without sstate. I don't have any immediate ideas on where to
> > > start
> > > looking into it, but I left the build in place, so if any of you
> > > can
> > > suggest experiments or things to look at, I'd be glad to help.
> > 
> > Oh, and I immediately got an idea after hitting 'send' :)
> > 
> > [akanavin@alma9-ty-2 build]$ gcc --version
> > gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3)
> > 
> > I'm going to try again, with buildtools-tarball. It may be that red
> > hat compiler is 'too old' anymore for rust.
> 
> ... and this worked. So the easiest way out is to update alma9 config
> to use buildtools.

Shouldn't rust complain if it doesn't work with old compilers? Are the
compiler requirements for rust documented anywhere? I'm reluctant to
throw buildtools at anything that breaks. In theory we also would need
to change the sanity.bbclass compiler versions tests and so on too :/

Cheers,

Richard