Bug 2338609
Summary: | meshlab fails to build with GCC 15 (-Wtemplate-body) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Siddhesh Poyarekar <sipoyare> |
Component: | meshlab | Assignee: | Eric Smith <spacewar> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 42 | CC: | mhroncok, releng, spacewar, spotrh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | meshlab-2023.12-11.fc42 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2025-04-01 16:08:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2300528, 2333037 |
Description
Siddhesh Poyarekar
2025-01-17 14:10:05 UTC
*** Bug 2340844 has been marked as a duplicate of this bug. *** This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42. FEDORA-2025-8b4a758d6d (meshlab-2023.12-11.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-8b4a758d6d FEDORA-2025-8b4a758d6d has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-8b4a758d6d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8b4a758d6d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-8b4a758d6d (meshlab-2023.12-11.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. |