From: "Alex Bennée" <alex.bennee@linaro.org>
To: Brian Cain <brian.cain@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, ltaylorsimpson@gmail.com,
matheus.bernardino@oss.qualcomm.com,
marco.liebel@oss.qualcomm.com, quic_mburton@quicinc.com,
sid.manning@oss.qualcomm.com, ale@rev.ng, anjo@rev.ng
Subject: Re: [PATCH v2] tests/docker: Update hexagon cross toolchain to 22.1.0
Date: Wed, 04 Mar 2026 17:49:32 +0000 [thread overview]
Message-ID: <87zf4no577.fsf@draig.linaro.org> (raw)
In-Reply-To: <20260303175444.1540049-1-brian.cain@oss.qualcomm.com> (Brian Cain's message of "Tue, 3 Mar 2026 09:54:44 -0800")
Brian Cain <brian.cain@oss.qualcomm.com> writes:
> Update the hexagon cross-compiler Docker container to use toolchain
> version 22.1.0, replacing the previous 12.Dec.2023 release. This release
> has valuable compiler and linker bugfixes, but more importantly it will
> enable us to target DSP arches up to v81.
>
> This requires upgrading the base image from Debian 11 to Debian 12
> because the new toolchain needs glibc >= 2.34. Additional changes
> to accommodate the new base image and toolchain:
>
> * Use DEB822 format for enabling deb-src
> * Add libc++1, libc++abi1, libunwind-14 runtime deps for the new
> toolchain
> * Add zstd for the new .tar.zst archive format
> * Replace pip3 install tomli with python3-tomli system package
> (Debian 12 enforces PEP 668)
>
> Signed-off-by: Brian Cain <brian.cain@oss.qualcomm.com>
Looks like there is enough around to put together another testing/next...
Queued to testing/next, thanks.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2026-03-04 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 17:54 [PATCH v2] tests/docker: Update hexagon cross toolchain to 22.1.0 Brian Cain
2026-03-03 18:07 ` Pierrick Bouvier
2026-03-03 18:10 ` Daniel P. Berrangé
2026-03-03 18:13 ` Brian Cain
2026-03-04 17:49 ` Alex Bennée [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zf4no577.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=brian.cain@oss.qualcomm.com \
--cc=ltaylorsimpson@gmail.com \
--cc=marco.liebel@oss.qualcomm.com \
--cc=matheus.bernardino@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=quic_mburton@quicinc.com \
--cc=sid.manning@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.