GCC11 in Fedora 34 defaults to producing DWARF5. This requires an update of libbacktrace which is bundled in this package.
I'm aware of that, but my scratch build attempting to patch it in still fails on other arches in essentially the same way as before.
FWIW, I've sync'd libbacktrace/dwarf.c with upstream and fixed the MD5 file. That seems to have done the trick on my scratch builds. I'm spinning official ones right now. I do think that a full sync of libbacktrace is advisable though, particularly for rawhide.
OK, my scratch build was patched with HEAD from https://github.com/ianlancetaylor/libbacktrace; apparently even though that's recently updated with history that looks quite similar, it's not in sync with gcc?
FEDORA-2021-b9b2172321 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-b9b2172321
FEDORA-2021-b9b2172321 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-b9b2172321` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-b9b2172321 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I went back and looked at the logs, and your patch is broken. It depends on dwarf2.h, which I don't think is public, so the compile fails and decides that libbacktrace is unavailable. The package is now effectively a no-op, and all tests are skipped.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.