* Zbigniew Jędrzejewski-Szmek: > On Wed, Oct 27, 2021 at 09:38:35AM +0200, Florian Weimer wrote: >> * Ben Cotton: >> >> > https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects >> > >> > == Summary == >> > All binaries (executables and shared libraries) are annotated with an >> > ELF note that identifies the rpm for which this file was built. This >> > allows binaries to be identified when they are distributed without any >> > of the rpm metadata. `systemd-coredump` uses this to log package >> > versions when reporting crashes. >> >> Can we enhance this to collect the package versions of all code that is >> linked statically? > > Hmm, do you mean the general case of any library linked statically, or > the special case where have an rpm with a static version of the library > (libfoo-static) and build another rpm with this? The general case of any statically linked code. It could be libgcc, startup files, the non-shared bits of glibc, static-only libraries, or header-only C++ libraries. Thanks, Florian _______________________________________________ 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
