On Wed, Sep 17, 2025 at 11:14:41PM +0930, Joel Stanley wrote: > On Fri, 5 Sept 2025 at 16:50, Richard Henderson > <richard.hender...@linaro.org> wrote: > > > > On 9/4/25 13:06, Daniel Henrique Barboza wrote: > > > How hard it is to update the GCC version we're running in the docker > > > images for > > > "check-tcg"? We would like to use a RISC-V vector header that isn't > > > supported > > > ATM. > > If debian packages the gcc version, then it's easy: change > > > > gcc-riscv-linux-gnu > > > > to > > > > gcc-NN-riscv-linux-gnu > > The test that was failing uses debian-all-test-cross. This is based on > Debian 12 which maxes out at GCC 12. > > If we move to Debian 13, we get GCC 14. Something like this would do it:
Debian 12 is a supported platform for QEMU, so we should generally expect our tests to work on that. That said IIUC riscv didn't become officially supported in Debian until 13, so we can use that as a justification for an exception to the normal platform rule. > --- a/tests/docker/dockerfiles/debian-all-test-cross.docker > +++ b/tests/docker/dockerfiles/debian-all-test-cross.docker > @@ -6,7 +6,7 @@ > # basic compilers for as many targets as possible. We shall use this > # to build and run linux-user tests on GitLab > # > -FROM docker.io/library/debian:12-slim > +FROM docker.io/library/debian:13-slim > > Is updating the distro something we would consider for this development cycle? > > Cheers, > > Joel > With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
