# Slicer Build Environment Upgraded to \`qt5-almalinux8-gcc14\`

**URL:** <https://discourse.slicer.org/t/slicer-build-environment-upgraded-to-qt5-almalinux8-gcc14/43802>\
**Category:** Development\
**Tags:** python, package, nightlybuild, extensions\
**Created:** [July 22, 2025, 5:19am UTC](https://discourse.slicer.org/t/slicer-build-environment-upgraded-to-qt5-almalinux8-gcc14/43802 "2025-07-22T05:19:42Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 8, 2025, 3:10pm UTC](https://discourse.slicer.org/t/slicer-build-environment-upgraded-to-qt5-almalinux8-gcc14/43802/6 "2025-08-08T15:10:57Z")

</div>

Can someone at Kitware confirm that the issue is not in some cache or something else leftover on the factory machines that need to be reset?

It is not the first time we have mysterious errors, and I think in the past there were cases when those were fixed by some magic by factory machines maintainers.

---

_[View the full topic](https://discourse.slicer.org/t/slicer-build-environment-upgraded-to-qt5-almalinux8-gcc14/43802)._