On 30/03/21 18:24 -0400, Omair Majid wrote:
Hi,
Jonathan Wakely <jwakely@xxxxxxxxxxxxxxxxx> writes:
Due to an unplanned ABI break that I caused in libstdc++, I will soon
start to rebuild the packages listed below. This rebuild will remove
references to some symbols in libstdc++.so which do not work as
intended, and so will not be present in the final gcc-11.1.0 release.
See https://bugzilla.redhat.com/show_bug.cgi?id=1937698 for reference.
Package maintainers should not need to do anything, but will see a
%release bump and a rebuild.
dotnet3.1
I am bit surprised that dotnet3.1 is in that list but not dotnet5.0.
If that's a new-ish package it might not be present in Florian's
database of packages that he searched for uses of the bad symbols.
Another possibility is that it wasn't rebuilt during the window when
those symbols were in libstdc++.so, or it has already been rebuilt
with the new GCC that fixes the problem.
Or maybe it just doesn't use std::call_once in the new version.
Is there some way I can confirm whether a package (like dotnet5.0) is
affected or not?
You can check if any binaries in your package depend on either ofthe
two symbols listed in the bugzilla report above:
_ZNSt9once_flag11_M_activateEv
_ZNSt9once_flag9_M_finishEb
You can use objdump -T or nm -D on the binary and grep for the
symbols, e.g. nm -D libfoo.so | grep _ZNSt9once_flag
If it should have been in my list then please let me know, or just
bump+build it yourself.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
