On 9/14/26 13:14, Simon Josefsson wrote:
Matthias Klose <[email protected]> writes:
On 9/14/26 10:14, Simon Josefsson wrote:
Hi
I noticed packages depending on clang-19 have been triggered for
autoremoval now. I want to update tillitis-tkey-libs and
tillitis-tkey-device-signer to use a newer clang.
But which version of clang?
Testing has clang 21, 22 and unstable also have 23.
Has it been decided what forky will ship with?
I can't say anything about the default clang version, however I will
maintain LLVM 21 for forky, because it's used by the GCC offloading,
and for the python just-in-time feature.
I have already got the approval from the security team, that shipping
multiple LLVM versions is not an issue from their side.
Thanks. Out of curiosity, why doesn't 22 or 23 solve your problem?
I'm using a version that I know is working for these, and where the LLVM
version was released before the Python or GCC upstream releases. Saves
me work, and gets you stability. For Python we'll have a lot of other
work to do with 3.15 for the forky release.
Are you or someone else planning to maintain clang 22 or 23 for forky?
No, I didn't commit to maintain 22 or another newer version yet. Busy
enough with the GNU toolchain. Likely I'll do the same thing with
another LLVM version for duke (forky+1).
Matthias
