Bug 1923625
| Summary: | openxr: FTBFS in Fedora rawhide/f34 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
| Component: | openxr | Assignee: | Luya Tshimbalanga <luya_tfz> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 34 | CC: | law, luya_tfz, negativo17 | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | openxr-1.0.16-1.fc33 openxr-1.0.16-1.fc34 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2021-05-21 03:12:29 UTC | Type: | --- | ||||||||
| 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: | 1868278 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Fedora Release Engineering
2021-02-01 17:20:48 UTC
Created attachment 1753825 [details]
build.log
file build.log too big, will only attach last 32768 bytes
Created attachment 1753826 [details]
root.log
file root.log too big, will only attach last 32768 bytes
Created attachment 1753827 [details]
state.log
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34. It seems to me that if openxr is going to use std::experimental::filesystem..., then it needs to link libstdc++fs. Alternatively it could use std::filesystem (ie, no experimental). Either way, this is a package issue, not a GCC issue. FEDORA-2021-37419f07ce has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-37419f07ce FEDORA-2021-3df9a95b52 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3df9a95b52 FEDORA-2021-37419f07ce has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-37419f07ce` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-37419f07ce See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-3df9a95b52 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-3df9a95b52` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-3df9a95b52 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-37419f07ce has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-3df9a95b52 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. |